<?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: Inquiry: Custom Alert Based on Root Cause Pattern in Dynatrace Managed in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Custom-Alert-Based-on-Root-Cause-Pattern-in-Dynatrace-Managed/m-p/284735#M4370</link>
    <description>&lt;P&gt;Hi Radek,&lt;/P&gt;&lt;P&gt;Thanks a lot for your input &lt;span class="lia-unicode-emoji" title=":folded_hands:"&gt;🙏&lt;/span&gt;. I managed to find a solution that works without relying on log monitoring. Let me share the steps in case it helps others:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Steps I followed:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Create a Request Attribute&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Navigate to &lt;EM&gt;Settings → Service-side service monitoring → Request attributes&lt;/EM&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Add a new request attribute that captures the &lt;EM&gt;exception class&lt;/EM&gt; or &lt;EM&gt;error message&lt;/EM&gt; from the failing requests.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Create a Calculated Service Metric&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Go to &lt;EM&gt;Settings → Server-side service monitoring → Calculated service metrics&lt;/EM&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Create a new metric with:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Metric source&lt;/STRONG&gt; = the request attribute you created&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Unit&lt;/STRONG&gt; = Count&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Optional: Add a filter condition so it only counts when the error message contains your specific phrase.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Create a Custom Event for Alerting&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Navigate to &lt;EM&gt;Settings → Anomaly detection → Custom events for alerting&lt;/EM&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Create a new event with:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Metric&lt;/STRONG&gt; = the calculated service metric&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Threshold&lt;/STRONG&gt; = ≥ 1 (so if the error shows up at least once, it triggers an alert)&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Assign the right &lt;EM&gt;management zone&lt;/EM&gt; so the correct team gets the alert.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Result:&lt;/STRONG&gt;&lt;BR /&gt;Now, even if Dynatrace doesn’t automatically generate a problem card, an alert will still be raised whenever this specific error message appears.&lt;/P&gt;&lt;P&gt;Hopefully this will be useful for others facing the same scenario&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":victory_hand:"&gt;✌️&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Aug 2025 10:09:22 GMT</pubDate>
    <dc:creator>Aboud1</dc:creator>
    <dc:date>2025-08-26T10:09:22Z</dc:date>
    <item>
      <title>Custom Alert Based on Root Cause Pattern in Dynatrace Managed</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Custom-Alert-Based-on-Root-Cause-Pattern-in-Dynatrace-Managed/m-p/282722#M4354</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hello All,&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;is it possible to configure a &lt;STRONG&gt;custom alert&lt;/STRONG&gt; in Dynatrace Managed based on a &lt;STRONG&gt;specific pattern appearing in the root cause section of a problem&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;We are trying to build an alerting rule that detects &lt;STRONG&gt;certain exception messages&lt;/STRONG&gt; or &lt;STRONG&gt;specific error text patterns&lt;/STRONG&gt; that appear under the &lt;EM&gt;Problem &amp;gt; Root cause&lt;/EM&gt; section.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;Example (for illustration only):&lt;/H3&gt;
&lt;P&gt;it shows a case where the root cause includes the following pattern:&lt;/P&gt;
&lt;DIV class=""&gt;
&lt;DIV class=""&gt;&lt;SPAN&gt;Error &lt;SPAN class=""&gt;while&lt;/SPAN&gt; creating customer interaction &lt;SPAN class=""&gt;record&lt;/SPAN&gt; &lt;SPAN class=""&gt;for&lt;/SPAN&gt; &lt;SPAN class=""&gt;product&lt;/SPAN&gt;:&lt;SPAN class=""&gt;XXXXX&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;And the related exception is:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV class=""&gt;
&lt;DIV class=""&gt;java.lang.IllegalArgumentException&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;We are &lt;STRONG&gt;not trying to create an alert for this specific case&lt;/STRONG&gt;, but it is &lt;STRONG&gt;a good example&lt;/STRONG&gt; of the type of root cause pattern we would like to monitor and alert on.&lt;/P&gt;
&lt;P&gt;We want to know if there is &lt;STRONG&gt;any method or workaround&lt;/STRONG&gt; that allows us to:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;Alert based on specific keywords or patterns in the &lt;STRONG&gt;Problem root cause section&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Create custom events if a certain &lt;STRONG&gt;exception type or message text&lt;/STRONG&gt; is detected.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;HR /&gt;
&lt;H3&gt;Environment:&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Dynatrace Managed&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;Logs ingestion: &lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Not enabled/preserved&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR /&gt;
&lt;P&gt;Looking forward to your guidance.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jan 2026 12:44:32 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Custom-Alert-Based-on-Root-Cause-Pattern-in-Dynatrace-Managed/m-p/282722#M4354</guid>
      <dc:creator>Aboud1</dc:creator>
      <dc:date>2026-01-05T12:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Inquiry: Custom Alert Based on Root Cause Pattern in Dynatrace Managed</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Custom-Alert-Based-on-Root-Cause-Pattern-in-Dynatrace-Managed/m-p/283038#M4357</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In Dynatrace Managed, it’s not possible to create alerts directly based on text found in the “root cause” section of a problem. However, a similar outcome can be achieved by configuring log monitoring and creating custom events based on specific phrases or exceptions, which can then trigger alerts.&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;</description>
      <pubDate>Tue, 05 Aug 2025 05:00:48 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Custom-Alert-Based-on-Root-Cause-Pattern-in-Dynatrace-Managed/m-p/283038#M4357</guid>
      <dc:creator>radek_jasinski</dc:creator>
      <dc:date>2025-08-05T05:00:48Z</dc:date>
    </item>
    <item>
      <title>Re: Inquiry: Custom Alert Based on Root Cause Pattern in Dynatrace Managed</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Custom-Alert-Based-on-Root-Cause-Pattern-in-Dynatrace-Managed/m-p/284735#M4370</link>
      <description>&lt;P&gt;Hi Radek,&lt;/P&gt;&lt;P&gt;Thanks a lot for your input &lt;span class="lia-unicode-emoji" title=":folded_hands:"&gt;🙏&lt;/span&gt;. I managed to find a solution that works without relying on log monitoring. Let me share the steps in case it helps others:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Steps I followed:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Create a Request Attribute&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Navigate to &lt;EM&gt;Settings → Service-side service monitoring → Request attributes&lt;/EM&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Add a new request attribute that captures the &lt;EM&gt;exception class&lt;/EM&gt; or &lt;EM&gt;error message&lt;/EM&gt; from the failing requests.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Create a Calculated Service Metric&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Go to &lt;EM&gt;Settings → Server-side service monitoring → Calculated service metrics&lt;/EM&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Create a new metric with:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Metric source&lt;/STRONG&gt; = the request attribute you created&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Unit&lt;/STRONG&gt; = Count&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Optional: Add a filter condition so it only counts when the error message contains your specific phrase.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Create a Custom Event for Alerting&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Navigate to &lt;EM&gt;Settings → Anomaly detection → Custom events for alerting&lt;/EM&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Create a new event with:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Metric&lt;/STRONG&gt; = the calculated service metric&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Threshold&lt;/STRONG&gt; = ≥ 1 (so if the error shows up at least once, it triggers an alert)&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Assign the right &lt;EM&gt;management zone&lt;/EM&gt; so the correct team gets the alert.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Result:&lt;/STRONG&gt;&lt;BR /&gt;Now, even if Dynatrace doesn’t automatically generate a problem card, an alert will still be raised whenever this specific error message appears.&lt;/P&gt;&lt;P&gt;Hopefully this will be useful for others facing the same scenario&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":victory_hand:"&gt;✌️&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Aug 2025 10:09:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Custom-Alert-Based-on-Root-Cause-Pattern-in-Dynatrace-Managed/m-p/284735#M4370</guid>
      <dc:creator>Aboud1</dc:creator>
      <dc:date>2025-08-26T10:09:22Z</dc:date>
    </item>
  </channel>
</rss>

