22 Sep 2025
10:34 AM
- last edited on
23 Sep 2025
05:57 AM
by
MaciejNeumann
In Dynatrace managed, currently, OS services do not inherit tags from their parent host, which makes downtime management very difficult. It would be valuable if OS services could automatically inherit host tags, upon creation or onboarding. This would reduce manual tagging, simplify automation, and ensure consistent monitoring and dashboards.
Solved! Go to Solution.
22 Sep 2025 01:18 PM
Hi,
you can approach this in two ways. One option is described in the discussion that AntonPineiro shared.
The second option is to leverage metadata. For example, you can add a custom metadata key/value pair during OneAgent installation and then create an auto-tag rule based on that metadata.
Additionally, if the monitored environment is Kubernetes, you can map Kubernetes labels directly to Dynatrace tags, which helps keep tagging consistent across hosts, processes, and services.
14 Nov 2025 02:40 PM
Team, my requirement is apply a dynamic auto tag with Host Name for associated OS services, so that it can be used in different places for example maintenance windows. Please help on how this can be acheived
14 Nov 2025 03:12 PM
You won’t be able to stamp the OS service with a host-name tag directly, but this is exactly what management zones are for.
Here example scenario:
At First Tag your hosts
Make sure the hosts have a tag you can use (for example based on host name, metadata, host group, environment, etc.).
Then Create a management zone based on host tags
Create an MZ rule that matches the host tag / host name.
In the rule, enable propagation so that the zone also includes:
the process groups running on those hosts, and
the services/OS services on those process groups.
and last step. Use the management zone in maintenance windows