Dynatrace OneAgent automatically discovers components in your environment, such as process groups, services and real user applications. Not only can these entities be auto-discovered, their underlying technologies can also be accurately identified (for example, Apache HTTP server, IBM WebSphere, and much more). As part of this auto-detection, Dynatrace discovers network topology as well. Once traffic is monitored, Dynatrace detects also load balancers and proxies. Moreover, Dynatrace supports 3rd party integrations, thus augmenting this data with topology and monitoring information from AWS, VMware, Azure, OpenStack, and more.
Managing such a huge amount of information, however, and organizing such large monitoring environments is a real challenge. To effectively cope with this challenge, Dynatrace supports tags and metadata. Tags and metadata enable you to organize your monitored environments in a meaningful way. Tags in Dynatrace are basically labels or markers while metadata are key/value pairs that are inherent to any monitored entity. Metadata are mainly used for defining extra information for entities while tags are used for organizing entities. You can also create tags based on metadata. In general, although tags and metadata are closely related, they are different concepts and are created and used in a different way.
Understand the difference between tags and metadata in Dynatrace.
Learn when it's recommended to use tags that leverage auto-detected metadata, as well as best practices for enriching Dynatrace monitoring with additional metadata.
Optimize auto-tagging and management-zone rules to speed up the automatic assignment process.
Find out how to define and apply tags manually and automatically.
Find out how Dynatrace enables you to define tags based on environment variables.
Automatically organize and filter all your monitored applications by applying tags from your Cloud Foundry environment.
Organize and filter your monitored applications by importing labels and annotations from your Kubernetes/OpenShift environment.
Organize and filter your monitored applications by importing labels and annotations from your Kubernetes/OpenShift environment.
Learn how to tag and set additional properties for a monitored host.
Configure your own process-related metadata based on the unique needs of your organization or environment.