Dynatrace automatically detects and displays lots of metadata values related to the processes that run in your environment—including version numbers, port numbers, and the name of the script or JAR file that launches each process (see images below).
Dynatrace enables you to use these metadata values to automate tagging as well as to use environment variables to supply tags. Dynatrace even allows you to define your own metadata based on your organization’s or environment’s unique needs.
Define metadata via environment variables
You can now define an environment variable called
DT_CUSTOM_PROP on either the process or host level. The format of the variable is simple, comprised of key/value pairs (for example,
DT_CUSTOM_PROP=Department=Acceptance Stage=Sprint). These variables must be visible to the respective process at startup. Once in place, the metadata values appear on each respective Process and Process group page (see example below).
To customize the process group of IIS you will need to define an environment variable that you can use within the scope of this rule. To set up an environment variable in IIS version 10 or later, see Environment variables. To set up an environment variable in IIS versions earlier than 10, see ApplicationPoolIdentity Environment variables IIS.
To customize process grouping for Windows services, you'll need to create a key called
Environment of type
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<servicename>. The value of the
Environment key may contain multiple entries like in the following example:
Using annotations in Kubernetes