<?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 Davis Anomaly Detection Not Triggering When VM Changes from PoweredOn to PoweredOff State in Extensions</title>
    <link>https://community.dynatrace.com/t5/Extensions/Davis-Anomaly-Detection-Not-Triggering-When-VM-Changes-from/m-p/305386#M7438</link>
    <description>&lt;P&gt;Hi Folks,&lt;/P&gt;&lt;P&gt;I have configured VM availability monitoring using the &lt;STRONG&gt;vmware.vm.availability&lt;/STRONG&gt; metric with the following filter conditions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;vm.power.state = PoweredOn&lt;/LI&gt;&lt;LI&gt;vm.connection.state = connected&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The purpose of this filter is to exclude VMs that are &lt;STRONG&gt;Powered Off but still connected&lt;/STRONG&gt;, which is commonly observed with decommissioned VMs.&lt;/P&gt;&lt;P&gt;We have tested this configuration, and during testing we noticed that when a VM transitions to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;vm.power.state = PoweredOff&lt;/LI&gt;&lt;LI&gt;vm.connection.state = connected&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;the VM is filtered out of the result set, and consequently no alert is triggered.&lt;/P&gt;&lt;P&gt;Has anyone encountered a similar situation and successfully configured and validated &lt;STRONG&gt;Davis Anomaly Detection&lt;/STRONG&gt; for this use case? Alternatively, is there another recommended approach to achieve the desired alerting behavior?&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;&lt;STRONG&gt;AK&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 18 Oct 2026 09:50:44 GMT</pubDate>
    <dc:creator>AK</dc:creator>
    <dc:date>2026-10-18T09:50:44Z</dc:date>
    <item>
      <title>Davis Anomaly Detection Not Triggering When VM Changes from PoweredOn to PoweredOff State</title>
      <link>https://community.dynatrace.com/t5/Extensions/Davis-Anomaly-Detection-Not-Triggering-When-VM-Changes-from/m-p/305386#M7438</link>
      <description>&lt;P&gt;Hi Folks,&lt;/P&gt;&lt;P&gt;I have configured VM availability monitoring using the &lt;STRONG&gt;vmware.vm.availability&lt;/STRONG&gt; metric with the following filter conditions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;vm.power.state = PoweredOn&lt;/LI&gt;&lt;LI&gt;vm.connection.state = connected&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The purpose of this filter is to exclude VMs that are &lt;STRONG&gt;Powered Off but still connected&lt;/STRONG&gt;, which is commonly observed with decommissioned VMs.&lt;/P&gt;&lt;P&gt;We have tested this configuration, and during testing we noticed that when a VM transitions to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;vm.power.state = PoweredOff&lt;/LI&gt;&lt;LI&gt;vm.connection.state = connected&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;the VM is filtered out of the result set, and consequently no alert is triggered.&lt;/P&gt;&lt;P&gt;Has anyone encountered a similar situation and successfully configured and validated &lt;STRONG&gt;Davis Anomaly Detection&lt;/STRONG&gt; for this use case? Alternatively, is there another recommended approach to achieve the desired alerting behavior?&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;&lt;STRONG&gt;AK&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Oct 2026 09:50:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/Davis-Anomaly-Detection-Not-Triggering-When-VM-Changes-from/m-p/305386#M7438</guid>
      <dc:creator>AK</dc:creator>
      <dc:date>2026-10-18T09:50:44Z</dc:date>
    </item>
  </channel>
</rss>

