<?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 Custom disk-detection rule overwrites other settings? in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Custom-disk-detection-rule-overwrites-other-settings/m-p/114573#M1122</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Can someone confirm, that the custom disk-detection rules overwrite other settings? So e.g.&lt;/P&gt;
&lt;P&gt;1. I have a host that's not using host group anomaly detection, it has a customized setup.&lt;/P&gt;
&lt;P&gt;2. Then I modify one specific drive to have low disk space detection off.&lt;/P&gt;
&lt;P&gt;3. If a custom disk-detection rule applies to that host group and that drive, it will essentially re-enable that drive's low disk space detection / alerting?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;That is at least what it appears to me. That's a bit problematic, because the custom rules are pretty rigid, and don't allow the exclusion of single hosts or drives. So you can't use them as a general template and then do some modifications host per host and drive per drive. It's starting to look easier to just ditch the custom rules, and manually modify each host.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 19 May 2021 10:19:43 GMT</pubDate>
    <dc:creator>kalle_lahtinen</dc:creator>
    <dc:date>2021-05-19T10:19:43Z</dc:date>
    <item>
      <title>Custom disk-detection rule overwrites other settings?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Custom-disk-detection-rule-overwrites-other-settings/m-p/114573#M1122</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Can someone confirm, that the custom disk-detection rules overwrite other settings? So e.g.&lt;/P&gt;
&lt;P&gt;1. I have a host that's not using host group anomaly detection, it has a customized setup.&lt;/P&gt;
&lt;P&gt;2. Then I modify one specific drive to have low disk space detection off.&lt;/P&gt;
&lt;P&gt;3. If a custom disk-detection rule applies to that host group and that drive, it will essentially re-enable that drive's low disk space detection / alerting?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;That is at least what it appears to me. That's a bit problematic, because the custom rules are pretty rigid, and don't allow the exclusion of single hosts or drives. So you can't use them as a general template and then do some modifications host per host and drive per drive. It's starting to look easier to just ditch the custom rules, and manually modify each host.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 May 2021 10:19:43 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Custom-disk-detection-rule-overwrites-other-settings/m-p/114573#M1122</guid>
      <dc:creator>kalle_lahtinen</dc:creator>
      <dc:date>2021-05-19T10:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: Custom disk-detection rule overwrites other settings?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Custom-disk-detection-rule-overwrites-other-settings/m-p/114574#M1123</link>
      <description>&lt;P&gt;Why not use the global host + tag option together with disk naming rules? Otherwise you can always override a single disk on a host of course. &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Feb 2019 07:17:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Custom-disk-detection-rule-overwrites-other-settings/m-p/114574#M1123</guid>
      <dc:creator>wolfgang_beer</dc:creator>
      <dc:date>2019-02-26T07:17:21Z</dc:date>
    </item>
  </channel>
</rss>

