topic Re: Default behavior of web checks in Synthetic Monitoring

Default behavior of web checks

thierry_chea1 — Wed, 03 Jan 2024 13:54:42 GMT

Hello,

According to the documentation, I saw that "Browser monitors alert you when your application becomes inaccessible or when baseline performance degrades significantly". Is Dynatrace considering that the web check fails if the HTTP response code is different of a 2XX type ?

Regards,

Re: Default behavior of web checks

Philipp_Kastner — Tue, 09 Jan 2018 11:32:43 GMT

Hi Thierry,

yes, a browser monitor (formerly web check) also fails for status codes between 400 to 599.

Kind regards, Philipp

Re: Default behavior of web checks

thierry_chea1 — Tue, 09 Jan 2018 13:00:48 GMT

Hi Philipp,

Thanks for the reply. I am wondering if it will be possible to specify a range of HTTP status code for validating a specific webcheck in the next releases ?

Regards,

Re: Default behavior of web checks

hayden_miedema — Wed, 10 Jan 2018 19:34:06 GMT

That is correct Thierry. Dynatrace's browser monitors are flagged as failures if a typical HTTP error status code is returned (coded 400-599).

What is your use case here? Are you responding with a not-failure status code for failures? Or vice versa?

Regards,

Hayden

Re: Default behavior of web checks

thierry_chea1 — Mon, 15 Jan 2018 09:53:06 GMT

Hello Hayden,

I would like to define a specific range of status code for failures just like "Services" where we can set it in the "Service settings". Is this kind of feature planned in the next releases ?

Regards,