<?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 Re: Exclude specific VMware ESXi host in the problems card. in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Exclude-specific-VMware-ESXi-host-in-the-problems-card/m-p/296528#M38803</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;I don’t think there is a native way to exclude only one specific ESXi host directly in the VMware anomaly detection settings, because that configuration is environment-scoped rather than host-scoped.&lt;BR /&gt;The cleanest workaround is to tag that host and create a maintenance window scoped to that tag, using Disable problem detection. That way Dynatrace won’t create problem cards for that host.&lt;BR /&gt;If the goal is only to suppress notifications, but not the problem itself, a separate management zone and alerting profile based on tags would also work.&lt;BR /&gt;IMO, what &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/73905"&gt;@lubrman&lt;/a&gt; suggested is a good direction. If you can tag that specific ESXi host, I’d go with tag + maintenance window scoped only to that host, using Disable problem detection.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Mar 2026 10:36:03 GMT</pubDate>
    <dc:creator>t_pawlak</dc:creator>
    <dc:date>2026-03-23T10:36:03Z</dc:date>
    <item>
      <title>Exclude specific VMware ESXi host in the problems card.</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Exclude-specific-VMware-ESXi-host-in-the-problems-card/m-p/295870#M38745</link>
      <description>&lt;P&gt;One of our VMware ESXi hosts is consistently creating a problem card for "low datastore space". I want to exclude this specific ESXi host from creating a problem card because it is part of its operation and is becoming too noisy. Is this possible?&lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2026 07:22:56 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Exclude-specific-VMware-ESXi-host-in-the-problems-card/m-p/295870#M38745</guid>
      <dc:creator>blade</dc:creator>
      <dc:date>2026-03-09T07:22:56Z</dc:date>
    </item>
    <item>
      <title>Re: Exclude specific VMware ESXi host in the problems card.</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Exclude-specific-VMware-ESXi-host-in-the-problems-card/m-p/296454#M38799</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/79229"&gt;@blade&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;Is it possible to tag ESXi hosts in any way and then, based on those tags, create a maintenance window or a separate management zone with an alerting profile that would handle this?&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 08:57:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Exclude-specific-VMware-ESXi-host-in-the-problems-card/m-p/296454#M38799</guid>
      <dc:creator>lubrman</dc:creator>
      <dc:date>2026-03-20T08:57:48Z</dc:date>
    </item>
    <item>
      <title>Re: Exclude specific VMware ESXi host in the problems card.</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Exclude-specific-VMware-ESXi-host-in-the-problems-card/m-p/296528#M38803</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;I don’t think there is a native way to exclude only one specific ESXi host directly in the VMware anomaly detection settings, because that configuration is environment-scoped rather than host-scoped.&lt;BR /&gt;The cleanest workaround is to tag that host and create a maintenance window scoped to that tag, using Disable problem detection. That way Dynatrace won’t create problem cards for that host.&lt;BR /&gt;If the goal is only to suppress notifications, but not the problem itself, a separate management zone and alerting profile based on tags would also work.&lt;BR /&gt;IMO, what &lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/73905"&gt;@lubrman&lt;/a&gt; suggested is a good direction. If you can tag that specific ESXi host, I’d go with tag + maintenance window scoped only to that host, using Disable problem detection.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Mar 2026 10:36:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Exclude-specific-VMware-ESXi-host-in-the-problems-card/m-p/296528#M38803</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-03-23T10:36:03Z</dc:date>
    </item>
  </channel>
</rss>

