02 Aug 2022 07:54 AM - last edited on 11 Aug 2022 05:46 AM by MaciejNeumann
Your help in knowing why 404 errors are not displayed in WAS (WebSphere Application Server) in Dynatrace:
Does anyone know why these 404 errors are not shown?
Have you checked the services of the WAS directly, if you see the 404s there? It should show them, even though they don't count towards the failure rate on server site.
Maybe the selected Management Zone or Timeframe is not correct?
At the log level I can't see them. But if you put a proxy on a computer, there are if you can see the errors.
But not in Dynatrace.
The filters of the management zones and the schedules if they are correct.
if I filter it by request count if it gives information.
If just check the service were the request should land directly if they show up at all.
Maybe something before the first agent responds with the 4xx?
Validate and if we are consulting well in the management zone
We just don't see 404 errors, we do see 500 errors.
Do you know how the dynatrace agent does these searches for errors?
It seems that Dynatrace doesn't consider 404 errors as failures by default.
But you can edit the service settings to consider 404 HTTP response as failures.
I provide you some steps to do this
1. Locate the service in dynatrace
2. Edit failure detection settings
Also if you would like to this but globally for the tenant, you can configurate it in the tenant settings
settings >> server-side monitoring >> failure detection
Tell us if this works