topic Re: Synthetic http status codes check in Synthetic Monitoring

Synthetic http status codes check

Julius_Loman — Fri, 12 Mar 2021 09:13:52 GMT

In the synthetic tests (clickpath or browser) are there any built-in checks on the returned HTTP status codes? (e.g. failure if HTTP Code is above 400).
Or can the HTTP codes be somehow used in the content validation?

Re: Synthetic http status codes check

Philipp_Kastner — Tue, 24 Apr 2018 14:29:19 GMT

Hi Julius,

browser & clickpath monitors will automatically fail for response status codes 400 to 599.

Kind regards, Philipp

Re: Synthetic http status codes check

Julius_Loman — Tue, 24 Apr 2018 14:37:11 GMT

That's interesting since I'm running a browser test for about a year and yesterday the monitored website had an outage (for several hours) and Dynatrace did not notice the outage at all. The service resulted in HTTP code 503 (with valid HTML output showing an error page). I can see it in the run analysis, that Dynatrace got the error page, but no problem was generated and there is not an outage in the availability graph.

Re: Synthetic http status codes check

Philipp_Kastner — Mon, 27 Mar 2023 10:31:32 GMT

That should not happen. As soon as the main document requests returns an HTTP status code 503 Dynatrace detects an outage. (If it was not manually disabled for this specific monitor)

Could you please go ahead and open a support ticket so we can have a closer look?

Thanks, Philipp

Re: Synthetic http status codes check

Julius_Loman — Wed, 25 Apr 2018 10:38:37 GMT

I've opened a support case (SUP-8685). My further investigation of synthetic runs revealed that although the waterfall displayed in Dynatrace reflected the error page which actually was actually server, the screenshot did not. So this really seems to be an issue in the Dynatrace synthetic engine.

Re: Synthetic http status codes check

don_bonin — Wed, 27 Mar 2019 17:13:59 GMT

Also, if Dynatrace detects a 200 response from any of the requests in an action, a single 500 response among many 200 responses will NOT trigger an error. Phillipp may be correct about the "main document" response, but I know for a fact that other errors can slip by unless you directly check the response code.