I just started starting trying configuring alerts on Dynatrace Managed and i'm a little bit lost because i never did that.
What i want exactly is to receive a notification on my email everytime a HTTP 413 error occurs.
Can someone walk me through the steps to do so ?
Solved! Go to Solution.
So Alerts are a 2 part thing. 1st, You must created an alert profile. This can be found under settings > Alert Profiles - This defines what an alert grouping contains. 2nd, you Must make an alert Integration, this is the method of how an alert is sent out. This is done by going to settings > Integrations > Alert Integration. From there you will have a variety of methods, the most easiest is the email method.
Let me know if you need any assistance with this
Alert Integration (EMail): https://www.dynatrace.com/support/help/setup-and-configuration/integrations/third-party-integrations...
Unless you tag the process or service that has that error and then adjust the detection settings on that entity to alert on that error code. FOr example, Tag Service A with "Custom Alert 1" then adjust the detection settings to only alert on error codes 413, then go into the alert profile, and add a tag that states only things with the tag "Custom Alert 1".
There several moving parts here that need to be set up. Chad's answer will be what is required to get notified when certain events/problems occur but in order to have a specific event for occurrences of a 413 response you'd need to define a calculated service metric that is filtered down to when 413s occur only for the services you're interested.
You'd then use that in defining a custom event for alerting to tell Dynatrace to create a problem what your threshold is breached. Once the problem is showing up in Dynatrace you need to have the alerting profile and problem notifications set up properly to be notified about them.
Thank you so much,
The only problem with this solution is that you are limited to 100 services so you can't apply it on your whole environment
but least now i can see a possibility i should just try and limit the scope of the request capturing