cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Private Synthetic Time increase

SachinJindal
Helper

Is there any way to increase the timeout beyond 180 Sec from Private location? Our Application Page load is too slow.

 

Thanks

14 REPLIES 14

AntonPineiro
DynaMight Leader
DynaMight Leader

Hi,

Are you talking about a Browser clickpath event?

Best regards

❤️ Emacs ❤️ Vim ❤️ Bash ❤️ Perl

HannahM
Dynatrace Leader
Dynatrace Leader

No, 180s is the maximum timeout for Browser Monitor event. The only way to wait longer would be to use a timed event for the 1st event and then have a 2nd event after it that wait for whatever change you need to occur on the page to move on. 

What about JS code? I could works maybe

function sleep(ms) {
return new Promise(resolve => setTimeout(resolve, ms));
}

async function demo() {
for (let i = 0; i < 5; i++) {
console.log(`Waiting ${i} seconds...`);
await sleep(i * 1000);
}
console.log('Done');
}

demo();





How this code would help ? lets say i have a Button which is click on Next  and need to wait until page is loaded which is taking 4 mins.

 

Thanks

step 1. click on button
step 2 in JS wait for 5 min and validate that you got some xpah/dom loaded, set assert
step3,4,5 next logic

HannahM
Dynatrace Leader
Dynatrace Leader

This would not work as the hard timeout for an event (step) is 3 minutes)

Slawa
Advisor

BTW you are in private location, set desired timeout in config:
https://www.dynatrace.com/support/help/dynatrace-api/environment-api/synthetic-v2/synthetic-configur...

 

{
"bmMonitorTimeout": 1200000,
"bmStepTimeout": 240000
}

 

does Steptimeout allow more than 180 sec on private location?

there is my config above - 240 sec

getting an error with 240 , seems they have validation which wont allow beyond 180.

******************************************

"path": "bmStepTimeout",
"message": "Validation failed. Value out of range.",

  

You can ask support/CSM, maybe you have some restriction on account level 

HannahM
Dynatrace Leader
Dynatrace Leader

180s hard timeout per event is a platform limit. I see that Slawa was able to increase it which is odd, as I cannot find any internal documentation referring that being allowed. 
Please use the option I suggested where you break the wait across 2 events instead 

SachinJindal
Helper

@HannahM  any comments on above?

 

Thanks

180s is the maximum timeout for Browser Monitor event. The only way to wait longer would be to use a timed event for the 1st event and then have a 2nd event after it that wait for whatever change you need to occur on the page to move on. 

Featured Posts