topic Re: Can oneagent report on error url's (eg application is down page with and 200 OK) in Synthetic Monitoring

Can oneagent report on error url's (eg application is down page with and 200 OK)

henk_stobbe — Thu, 29 Aug 2024 09:30:34 GMT

I have an application with nicely gives a warning page if something is wrong. As an example when the database is full the application gives a nice error page with a 200 ok.

It would be nice if this was recognized by oneAgent

Henk

Re: Can oneagent report on error url's (eg application is down page with and 200 OK)

Philipp_Kastner — Wed, 07 Jun 2017 14:26:14 GMT

Hi Henk,

one possibility to catch this is to create a web check with content validation. If the error page shows up, the web check would fail and a problem is generated. You can find more details how to configure the content validation here: https://help.dynatrace.com/user-experience-monitor...

Kind regards, Philipp

Re: Can oneagent report on error url's (eg application is down page with and 200 OK)

henk_stobbe — Wed, 07 Jun 2017 14:34:46 GMT

Hi Philipp,

Great tip thx, unfortunately in this situation we do not have internet access, so I think no web checks in this environment (yet)

KR Henk

Re: Can oneagent report on error url's (eg application is down page with and 200 OK)

fstekelenburg — Thu, 29 Sep 2022 11:06:35 GMT

Private Synthetic would be the best option I guess. Webchecks from within your own perimeter.
(Writing) an extension might be another.

Actually I have a similar question, but then in regard to RUM.
According to this article pages with 200 ok and an application specific error message can not be captured within RUM
Can RUM JS capture or identify a custom error on a xhr request - Dynatrace Community

In another article there is talk of custom error/string detection captured from the users session via a string detection.
Solved: Form Validation Error Tracking - Dynatrace Community

Re: Can oneagent report on error url's (eg application is down page with and 200 OK)

Viachaslau — Thu, 29 Sep 2022 11:54:29 GMT

We faced with the same problem.
Decided to go with custom action for error event + action property as error message (this is for RUM)

For server side if exception raised - you will able to filter 200OK by exception type (this is applicable for proxies and gateways that raised errors in body with 200OK response)