<?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 Anomaly Alerts for 4xx alerts by request/endpoints in Dynatrace Classic in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Anomaly-Alerts-for-4xx-alerts-by-request-endpoints-in-Dynatrace/m-p/298623#M6300</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We want to get alerted on anomalous behaviour in our 4XX errors. In the particular, the ones affecting out front end and middleware.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Constraints:&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;We do not want to define 4XX errors as server-side as this will affect the failure rates and cause poor error detection to the mix of business/expected errors inherent to 4XX responses.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;We want to minimize the number of CSMs and Metric Events, including the volume of data ingested by a Metric Event&lt;/LI&gt;
&lt;LI&gt;Any solution &lt;I&gt;has &lt;/I&gt;to tell us which application, service &amp;amp; &amp;nbsp;HTTP response code is driving the issue &amp;nbsp;(ie dimensions to split)
&lt;UL&gt;
&lt;LI&gt;Preferably we can drill down the specific request/endpoint&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI&gt;Preferably, when an increase in 4XX errors occurs, a solution would be able to tell us what request/endpoint is driving the issue.&lt;/LI&gt;
&lt;LI&gt;Strong preference for anomaly detection vs static threshold&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestions for the recommended solution to the above problem statement in Dynatrace Classic, we do not have Grail/DPS.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Hari&lt;/P&gt;</description>
    <pubDate>Thu, 30 Apr 2026 06:53:28 GMT</pubDate>
    <dc:creator>harinhs1</dc:creator>
    <dc:date>2026-04-30T06:53:28Z</dc:date>
    <item>
      <title>Anomaly Alerts for 4xx alerts by request/endpoints in Dynatrace Classic</title>
      <link>https://community.dynatrace.com/t5/Alerting/Anomaly-Alerts-for-4xx-alerts-by-request-endpoints-in-Dynatrace/m-p/298623#M6300</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;We want to get alerted on anomalous behaviour in our 4XX errors. In the particular, the ones affecting out front end and middleware.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Constraints:&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;We do not want to define 4XX errors as server-side as this will affect the failure rates and cause poor error detection to the mix of business/expected errors inherent to 4XX responses.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;We want to minimize the number of CSMs and Metric Events, including the volume of data ingested by a Metric Event&lt;/LI&gt;
&lt;LI&gt;Any solution &lt;I&gt;has &lt;/I&gt;to tell us which application, service &amp;amp; &amp;nbsp;HTTP response code is driving the issue &amp;nbsp;(ie dimensions to split)
&lt;UL&gt;
&lt;LI&gt;Preferably we can drill down the specific request/endpoint&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI&gt;Preferably, when an increase in 4XX errors occurs, a solution would be able to tell us what request/endpoint is driving the issue.&lt;/LI&gt;
&lt;LI&gt;Strong preference for anomaly detection vs static threshold&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestions for the recommended solution to the above problem statement in Dynatrace Classic, we do not have Grail/DPS.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Hari&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2026 06:53:28 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Anomaly-Alerts-for-4xx-alerts-by-request-endpoints-in-Dynatrace/m-p/298623#M6300</guid>
      <dc:creator>harinhs1</dc:creator>
      <dc:date>2026-04-30T06:53:28Z</dc:date>
    </item>
  </channel>
</rss>

