Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ignore valid 5xx scenarios


Hi Team,


We came through few expected/valid scenarios of 5xx errors where we don’t want any error count against that but unfortunately they are also being captured on DT .

We tried to configure the system by following the provided link, which involved creating a rule to ignore the "good" responses. However, the configuration did not work out and we are still getting those errors as 5xx.


Please advise on this. 




DynaMight Champion
DynaMight Champion



Could you please past your configuration here?

Sharing Knowledge

DynaMight Champion
DynaMight Champion

You should exclude the exact HTTP 500 code from the first line.



But remember, here it will applied for all services in your environment.

If you want to do it for a specific services(s). you should apply it on the service(s).



Sharing Knowledge

Hi Malaik,


We have made the changes as you suggested, but still we can see the 503 http responses being captured. Attached the snapshot of last 2 hours requests for you reference .


Please let us know if any changes are required. 

DynaMight Champion
DynaMight Champion


This method will only exclude the http code from the list of errors but the request will remain captured.

Are you looking to not capture the request (trace) at all? if yes, I'm not sur that this is possible.


Sharing Knowledge

I'm thinking of a workaround that can be used, by creating web request naming rules, to rename all requests with status 503 to be named as the http status itself {HTTP-Status} (this is in case the original request name is not required and will be ignored), then mute the request with name 503.

After you mute a request,

Automatic alerts for the muted request will no longer be generated.
The muted request will be excluded from the service charts.

Certified Dynatrace Professional | Certified Dynatrace Services Delivery - Observability & CloudOps | Dynatrace Partner -

Hope you are doing wee @Mohamed_Hamdy 

I didnt suggest this for 2 reasons:

1- you should do it service by service (or via API) which is a huge work.

2- Not only http code 503 should be ignored but as requested all 5xx.


I think this should be reviewed (i didnt ask the why for this decision), but ignore all 5xx is not good for the health of the applications we can miss an important issues.

Sharing Knowledge

Hi @Malaik ,

I'm fine and I hope you are doing well too.

Of course, I agree with you that ignoring all 5xx is not good and not recommended, I've just added this workaround for specific HTTP status in specific cases. and on a certain service this will be easy, and using API globally is not that hard to do as well.

in the end, Dynatrace has multiple ways to configure things if it's not straightforward configurations.


Certified Dynatrace Professional | Certified Dynatrace Services Delivery - Observability & CloudOps | Dynatrace Partner -

Featured Posts