Does anyone know how to edit the anomaly detection settings for alerts like this?
HTTP error rate increase
The current error rate value of 12.1 was above your auto-baseline of 11.8.
So for example, if I would like that we only alert when the auto-baseline is breached by 100 % - meaning we need to see at least an error rate value of 2 * 11,8 = 23,6 before this alert is generated. Where can I define that?
Based on the info I've got so far, the HTTP errors are actually coming from the OneAgents at server-side, not from RUM (like everything else under the Applications menu). Does anyone know if there's any documentation about these HTTP error rate alerts for Applications? I was unable to find any. And to be clear, I'm not talking about which 4xx or 5xx responses are regarded as errors per app. I'm happy with the way that is configured. I just want to raise the alerting threshold, so that I don't get those HTTP error alerts as often as I currently do.
I've also created an RFE regarding this topic (https://community.dynatrace.com/t5/Dynatrace-product-ideas/RFE-ability-to-configure-Application-HTTP...), but since there's no activity or comments there, I thought I'd also separately ask about it in this section.
Solved! Go to Solution.
You can edit those on the application settings -> Anomaly Detection (to just one application) or globally under Settings -> Anomaly Detection -> Applications.
You can define the % deviation for error rates in there.
More details can be found here: https://www.dynatrace.com/support/help/how-to-use-dynatrace/problem-detection-and-analysis/problem-d...
Thanks Arturo! It would be great if we can get a confirmation from Dynatrace that it indeed works that way. Because so far I've got very contradicting information about this: both a Dynatrace consultant and a person from the in-product chat told me that I cannot edit this Application HTTP error rate anomaly detection under the Application's settings, only under Services settings. Which is why I'm slowly starting to lose my mind with this topic, since it seems that no one really knows how this works 😛
I understand the baseline is for all the errors, so the adjustment will affect to all of them, as defined on the error detection.
Here a blog post with more details on the topic: https://www.dynatrace.com/news/blog/extended-davis-awareness-of-http-and-custom-errors/
I think the UI is referencing the previous behavior (prior to v 200)