Request timeout for synthetic monitor in Dynatrace

[Jean-Pierre_Rio]

Hi all,

I want to monitor a slow page (response time >10s) with synthetic monitor in Dynatrace managed, but the request times out after 10s (Request timeout to xxxxxxxxxxxxxxxxxxx/192.168.122.100:443 after 10000 ms).

Is it possible to overwrite this timeout for this peculiar monitor ?

JP

[Konrad_Lisiecki]

@Jean-Pierre R. provided we're talking about private synthetic monitoring and depending on which monitor type you're referring to (wasn't specified in question), you can modify requests and connect timeouts used by your particular synthetic-enabled AG. This can be achieved by adding/modifying custom configuration files as below. There's however no possibility to overwrite settings per particular monitor.

Assuming default installation paths were used:

HTTP monitors settings

/var/lib/dynatrace/gateway/config/custom.properties

[synthetic]
requestTimeoutInMs = 10000
connectTimeoutInMs = 5000

Browser monitors settings

/var/lib/dynatrace/synthetic/config/user.properties

com.ruxit.vuc.http.httpClient.socketTimeoutMs=10000
com.ruxit.vuc.http.httpClient.connectTimeoutMs=5000

[manish_reddy]

Hi,

me also facing the connection timeout issue in http and brrowser monitors can this issue be solved by increasing the time as you mentioned above?

[ct_27]

Can anyone confirm if this discussion and proposed solution above are related to this configuration?

We have HTTP/HTTPS synthetic tests for which our company is ok with up to 120 second response times but this metric is causing a bunch of false alerts.   Yes, we increased it to 60 to take care of most issues but we need it to go higher.

[karanbirsingh]

Hey @Konrad_Lisiecki, 

It doesn't seem to work when we are configuring this in a private synthetic location. 
Also tried to find the same param in official docs but couldn't find it anywhere. 

Can you confirm if this is something that is still applicable and can be configured?

Thanks! 

[HannahM · Accepted solution]

These parameters are no longer used as we added the setting in to the request. So you can now use 'Adapt request timeout' option. See documentation

[Romanenkov_Al3x]

Thanks. Helpful.