Dynatrace allows you to define your own metadata based on the needs of your organization or environment. You can also define process group metadata using a Cloud Foundry service and reuse it across multiple applications.
Define Cloud Foundry service metadata
To define your own process group metadata, you can use one or more Cloud Foundry service instances that have the name
dynatrace as a substring. For example:
cf cups dynatrace-metadata -p "meta-data:owner"
You’re automatically prompted to provide values for certain metadata. To update more than one at a time, separate by comma.
cf cups dynatrace-metadata -p "meta-data:owner, meta-data:github-source, meta-data:step"
If your monitored Cloud Foundry application is available on GitHub, you can easily add a link to the respective GitHub repository using custom process group metadata. As shown in the example below, we’ve specified custom process group metadata for a sample monolithic application called TicketMonster (you can read up on this in the blog post Fearless Monolith to Microservices Migration – A guided journey by Johannes Bräuer). We’ve added the GitHub repository link of the TicketMonster application as a github-source property and we’ve also identified the application as the monolithic starting point for the “break-up journey” towards a microservices architecture.
If you’re leveraging Cloud Foundry buildpacks to integrate Dynatrace OneAgent into your application, specifying the buildpack version that was used to deploy the application can be helpful in understanding the features that are available as part of a buildpack release.
cf cups dynatrace-apps-only-metadata -p "meta-data:buildpack, meta-data:version"
If you want to compare the behavior of two application versions in a Blue-Green deployment, you can also use custom process group metadata to identify different application versions.
Note: In order to exploit the service instance
dynatrace-*-metadata) you must bind the instance to your application (for example,
cf bs ticket-monster dynatrace-metadata
Use custom process group metadata for organizing your Cloud Foundry applications
You can use your Cloud Foundry process group metadata as a placeholder when creating automatically applied tags (as shown in the example below) or for process group naming. The rule-based tag below will be added to the monolithic TicketMonster application and all related services. In this example, we’ve defined the custom process group
meta-data:step>monolith to be the tag value.