AppD Archive

Synthetic job does not run due to time limit of 5 min

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I have configured a sythetic job and scheduled it to run every 10 mins. When I look into the result it failed. The error is:

0.00s   [INFO]  Starting measurement [160511_Y2_6F8]
0.47s   [INFO]  Executing WebDriver script
300.47s [ERROR] Script timed out after 300 seconds

image.jpeg

Does this mean we cannot run test cases that take more than 5 mins?

Please advice how to run a job that takes over 5mins.

Thank you.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

as the Synthetic product stands today, 5 minutes (300 secs) is the upper limit and cannot be increased, I think. If you are a customer of AppDynamics' then suggest you open a ticket thru the portal and we will be able to raise a Change Request to make this user-specifiable (>300 secs). One thinking is that a job that runs for > 5 mins is possibly comprised of multiple smaller tasks, which should be individual jobs on the schedule themselves. What sort of a job / script is this that you are dealing with here Shantakumari? curious....thanks

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thanks for the response Hari, that was helpful.

I will see if we can break the job into smaller jobs or else I will raise a change request.

Thank you.

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...