topic Re: Http monitor - How to force to wait for next step in Synthetic Monitoring

Forced waiting for next step in HTTP Monitor

SabineR — Fri, 10 May 2024 14:54:11 GMT

Hello,

I developped an HTTP monitor.

In one step, I have to wait a few seconds before doing the next HTTP requests, and I have 2 issues:

1. Contrary to Browser monitors, we don't have the option "Amount of time to wait before the next event is triggered"

Are you planning to add it?

2. The only way I found to do a wait, was to use some not great Javascript codes.

And I got another issue: if I put more than 1000 ms, I obtain a Script execution timeout error.

I tried to change the option "Adapt request timout" to 10s (which is normally already the case).

But It doesn't work too: I don't know why, but the step can't take more than 1 second.

Is it a bug? Or is this restriction registered in another settings in Dynatrace?

If yes, where?

Many thanks in advance for your answer,

Kind Regards,

Sabine

Re: Http monitor - How to force to wait for next step

HannahM — Fri, 01 Mar 2024 10:36:14 GMT

1) I am not aware of any plans to add a wait option for HTTP Monitors.

2) There are some suggestions here for inserting a wait.
As you found the default timeout out for a pre- or post-execution script is 1s, so using the

https://postman-echo.com/delay/2

suggestion gets around this by using another request which you can adapt the timeout up to 60s.

We are planning to make the pre- or post-execution script timeout be modifiable (up to 10s). This is currently part of a preview, so if the postman alternative is not suitable you can speak to your CSM or Sales Exec about joining the HTTP Monitors Advanced Settings preview.

Re: Http monitor - How to force to wait for next step

SabineR — Fri, 01 Mar 2024 13:08:23 GMT

Thank you Hanna

Re: Http monitor - How to force to wait for next step

eleone88 — Thu, 18 Jul 2024 17:51:21 GMT

The only 'solution' that I could find re: a delay between steps in Dynatrace Synthetic Monitor is using https://postman-echo.com/delay/2. How/where do I use this, as a pre- or post-execution script, or as an HTTP standalone request between the two requests where a delay is required? How should it be configured/written within the request? I tried adding it as the latter, but it consistently fails with SSL_COMMUNICATION_ERROR.

Any help would be greatly appreciated!

Re: Http monitor - How to force to wait for next step

HannahM — Fri, 19 Jul 2024 09:10:54 GMT

Hi @eleone88 ,

requests cannot be added to pre- or post-execution scripts. The way to add the wait is to add another HTTP request in between the other 2. You need to set the request url to be https://postman-echo.com/delay/2.