<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Auto-tag OS services based on the Host tag in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/286505#M37633</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Sep 2025 04:57:44 GMT</pubDate>
    <dc:creator>Manisha_G</dc:creator>
    <dc:date>2025-09-23T04:57:44Z</dc:date>
    <item>
      <title>Auto-tag OS services based on the Host tag</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/286505#M37633</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Sep 2025 04:57:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/286505#M37633</guid>
      <dc:creator>Manisha_G</dc:creator>
      <dc:date>2025-09-23T04:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: Auto-tag OS services based on the Host tag</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/286507#M37634</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It was discussed &lt;A title="here" href="https://community.dynatrace.com/t5/Open-Q-A/Auto-tags-for-os-services/m-p/282510" target="_blank" rel="noopener"&gt;here&lt;/A&gt; also.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Mon, 22 Sep 2025 09:52:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/286507#M37634</guid>
      <dc:creator>AntonPineiro</dc:creator>
      <dc:date>2025-09-22T09:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: Auto-tag OS services based on the Host tag</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/286519#M37636</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;you can approach this in two ways. One option is described in the discussion that AntonPineiro shared.&lt;BR /&gt;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.&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Sep 2025 12:18:46 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/286519#M37636</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2025-09-22T12:18:46Z</dc:date>
    </item>
    <item>
      <title>Re: Auto-tag OS services based on the Host tag</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/289616#M37999</link>
      <description>&lt;P&gt;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.&amp;nbsp; Please help on how this can be acheived&lt;/P&gt;</description>
      <pubDate>Fri, 14 Nov 2025 14:40:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/289616#M37999</guid>
      <dc:creator>Vidhyasagar</dc:creator>
      <dc:date>2025-11-14T14:40:21Z</dc:date>
    </item>
    <item>
      <title>Re: Auto-tag OS services based on the Host tag</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/289619#M38000</link>
      <description>&lt;P&gt;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.&lt;BR /&gt;Here example scenario:&lt;/P&gt;&lt;P&gt;At First Tag your hosts&lt;BR /&gt;Make sure the hosts have a tag you can use (for example based on host name, metadata, host group, environment, etc.).&lt;/P&gt;&lt;P&gt;Then Create a management zone based on host tags&lt;/P&gt;&lt;P&gt;Create an MZ rule that matches the host tag / host name.&lt;/P&gt;&lt;P&gt;In the rule, enable propagation so that the zone also includes:&lt;/P&gt;&lt;P&gt;the process groups running on those hosts, and&lt;/P&gt;&lt;P&gt;the services/OS services on those process groups.&lt;/P&gt;&lt;P&gt;and last step. Use the management zone in maintenance windows&lt;/P&gt;</description>
      <pubDate>Fri, 14 Nov 2025 15:12:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/289619#M38000</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2025-11-14T15:12:44Z</dc:date>
    </item>
    <item>
      <title>Re: Auto-tag OS services based on the Host tag</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/290138#M38051</link>
      <description>&lt;P&gt;Yes mapping the OS services with management zone already works fine but with maintenance mode we cannot always rely on management zone always as maintenance of hosts will be taken up in groups for same application. it would be difficult to manage multiple management zones for single application.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 12:11:20 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Auto-tag-OS-services-based-on-the-Host-tag/m-p/290138#M38051</guid>
      <dc:creator>Vidhyasagar</dc:creator>
      <dc:date>2025-11-24T12:11:20Z</dc:date>
    </item>
  </channel>
</rss>

