<?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 How to Automatically Detect Process Failures in Dynamic Infrastructure in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/How-to-Automatically-Detect-Process-Failures-in-Dynamic/m-p/297626#M6266</link>
    <description>&lt;P&gt;Hello community,&lt;/P&gt;
&lt;P&gt;I am trying to configure a global availability alert for a specific infrastructure process, but I have hit a logical wall within Dynatrace SaaS.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The Goal:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I need to monitor the availability of several process thats is not running in all my servers (example: p_ctmag).&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;It is deployed across approximately 140 Linux servers.&lt;/LI&gt;
&lt;LI&gt;We do not have a static inventory of these servers, as the deployment is dynamic.&lt;/LI&gt;
&lt;LI&gt;Requirement: Trigger a "Process Unavailable" alert indicating the affected host if the p_ctmag process crashes on &lt;EM&gt;any&lt;/EM&gt; server that was running it.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;The problem:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Our infrastructure is heavily divided using Host Groups. By design, Dynatrace does not merge processes belonging to different Host Groups into a single Process Group. Consequently, I do not have one global Process Group to monitor, but dozens of isolated ones.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Failed Strategies:&lt;/STRONG&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Declarative Process Grouping:&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;I created a rule targeting the $eq(p_ctmag) executable. While the detection works perfectly, Dynatrace still separates the resulting Process Groups based on the underlying Host Groups. Because they remain fragmented, I cannot configure a centralized "Alert if any process becomes unavailable" anomaly detection rule.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Advanced Detection Rules:&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Not applicable. As per the documentation, these rules only apply to deep-monitored technologies (like Java or .NET) and do not work for native OS binaries like this one.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Process Availability Rules (with Auto-Tags):&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Since I lack a static inventory, I attempted to use &lt;EM&gt;Settings &amp;gt; Processes and containers &amp;gt; Process availability&lt;/EM&gt;. I configured a Host Auto-tag rule to dynamically tag any server running p_ctmag. Then, I scoped the Process Availability rule to that specific host tag.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;The logical flaw:&lt;/EM&gt; If the process dies on a server, that server dynamically loses the tag. Once the tag is lost, the host falls out of the availability rule's scope, and the alert either never triggers or auto-closes instantly.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;My Question:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Is there a native, fully dynamic way to monitor infrastructure OS process crashes distributed across multiple Host Groups without relying on manual tagging or maintaining static inventories?&lt;/P&gt;
&lt;P&gt;Any insights or architectural workarounds (even utilizing the API or DQL) would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;/P&gt;
&lt;P&gt;Victor&lt;/P&gt;</description>
    <pubDate>Tue, 14 Apr 2026 06:29:42 GMT</pubDate>
    <dc:creator>VictorRuiz</dc:creator>
    <dc:date>2026-04-14T06:29:42Z</dc:date>
    <item>
      <title>How to Automatically Detect Process Failures in Dynamic Infrastructure</title>
      <link>https://community.dynatrace.com/t5/Alerting/How-to-Automatically-Detect-Process-Failures-in-Dynamic/m-p/297626#M6266</link>
      <description>&lt;P&gt;Hello community,&lt;/P&gt;
&lt;P&gt;I am trying to configure a global availability alert for a specific infrastructure process, but I have hit a logical wall within Dynatrace SaaS.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The Goal:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;I need to monitor the availability of several process thats is not running in all my servers (example: p_ctmag).&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;It is deployed across approximately 140 Linux servers.&lt;/LI&gt;
&lt;LI&gt;We do not have a static inventory of these servers, as the deployment is dynamic.&lt;/LI&gt;
&lt;LI&gt;Requirement: Trigger a "Process Unavailable" alert indicating the affected host if the p_ctmag process crashes on &lt;EM&gt;any&lt;/EM&gt; server that was running it.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;The problem:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Our infrastructure is heavily divided using Host Groups. By design, Dynatrace does not merge processes belonging to different Host Groups into a single Process Group. Consequently, I do not have one global Process Group to monitor, but dozens of isolated ones.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Failed Strategies:&lt;/STRONG&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Declarative Process Grouping:&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;I created a rule targeting the $eq(p_ctmag) executable. While the detection works perfectly, Dynatrace still separates the resulting Process Groups based on the underlying Host Groups. Because they remain fragmented, I cannot configure a centralized "Alert if any process becomes unavailable" anomaly detection rule.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Advanced Detection Rules:&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Not applicable. As per the documentation, these rules only apply to deep-monitored technologies (like Java or .NET) and do not work for native OS binaries like this one.&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Process Availability Rules (with Auto-Tags):&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Since I lack a static inventory, I attempted to use &lt;EM&gt;Settings &amp;gt; Processes and containers &amp;gt; Process availability&lt;/EM&gt;. I configured a Host Auto-tag rule to dynamically tag any server running p_ctmag. Then, I scoped the Process Availability rule to that specific host tag.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;The logical flaw:&lt;/EM&gt; If the process dies on a server, that server dynamically loses the tag. Once the tag is lost, the host falls out of the availability rule's scope, and the alert either never triggers or auto-closes instantly.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;My Question:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Is there a native, fully dynamic way to monitor infrastructure OS process crashes distributed across multiple Host Groups without relying on manual tagging or maintaining static inventories?&lt;/P&gt;
&lt;P&gt;Any insights or architectural workarounds (even utilizing the API or DQL) would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;/P&gt;
&lt;P&gt;Victor&lt;/P&gt;</description>
      <pubDate>Tue, 14 Apr 2026 06:29:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/How-to-Automatically-Detect-Process-Failures-in-Dynamic/m-p/297626#M6266</guid>
      <dc:creator>VictorRuiz</dc:creator>
      <dc:date>2026-04-14T06:29:42Z</dc:date>
    </item>
  </channel>
</rss>

