# Request timeout for synthetic monitor in Dynatrace

**URL:** <https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561>\
**Category:** Synthetic Monitoring\
**Tags:** synthetic-monitoring\
**Created:** [November 14, 2019, 1:51pm UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561 "2019-11-14T13:51:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jean-Pierre\_Rio](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@Jean-Pierre\_Rio](https://community.dynatrace.com/u/Jean-Pierre_Rio)\
**Post date:** [November 14, 2019, 1:51pm UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561/1 "2019-11-14T13:51:33Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Konrad\_Lisiecki](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/konrad_lisiecki/32/12216_2.png) [@Konrad\_Lisiecki](https://community.dynatrace.com/u/Konrad_Lisiecki)\
**Post date:** [November 21, 2019, 1:17pm UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561/2 "2019-11-21T13:17:26Z")

</div>

[@Jean-Pierre R.](https://answers.dynatrace.com/users/4198/view.html) 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_

```auto
[synthetic]<br>requestTimeoutInMs = 10000<br>connectTimeoutInMs = 5000<br>

```

**Browser monitors** settings

_/var/lib/dynatrace/synthetic/config/user.properties_

```auto
com.ruxit.vuc.http.httpClient.socketTimeoutMs=10000<br>com.ruxit.vuc.http.httpClient.connectTimeoutMs=5000<br>

```

---

<div class="post-metadata">

**Author:** ![manish\_reddy](https://avatars.discourse-cdn.com/v4/letter/m/aca169/32.png) [@manish\_reddy](https://community.dynatrace.com/u/manish_reddy)\
**Post date:** [April 13, 2020, 4:41pm UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561/3 "2020-04-13T16:41:59Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![ct\_27](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/ct_27/32/10499_2.png) [@ct\_27](https://community.dynatrace.com/u/ct_27)\
**Post date:** [December 6, 2021, 5:45pm UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561/4 "2021-12-06T17:45:29Z")

</div>

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

 ![ct_27_0-1638812663936.png](https://global.discourse-cdn.com/dynatrace/original/3X/9/8/98fa43151fa5035a4e0a3b0b164491c1648885bc.png)

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.&nbsp; &nbsp;Yes, we increased it to 60 to take care of most issues but we need it to go higher.

---

<div class="post-metadata">

**Author:** ![karanbirsingh](https://avatars.discourse-cdn.com/v4/letter/k/f05b48/32.png) [@karanbirsingh](https://community.dynatrace.com/u/karanbirsingh)\
**Post date:** [August 3, 2022, 1:17pm UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561/5 "2022-08-03T13:17:36Z")

</div>

Hey [@Konrad\_Lisiecki](https://community.dynatrace.com/user/2922),

It doesn’t seem to work when we are configuring this in a private synthetic location.&nbsp;  
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!

---

<div class="post-metadata">

**Author:** ![hannahmac](https://avatars.discourse-cdn.com/v4/letter/h/dec6dc/32.png) [@hannahmac](https://community.dynatrace.com/u/hannahmac)\
**Post date:** [August 3, 2022, 1:25pm UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561/6 "2022-08-03T13:25:18Z")

</div>

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](https://www.dynatrace.com/support/help/how-to-use-dynatrace/synthetic-monitoring/http-monitors/configure-http-monitors#http-additional-options)

---

<div class="post-metadata">

**Author:** ![Romanenkov\_Al3x](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/romanenkov_al3x/32/36257_2.png) [@Romanenkov\_Al3x](https://community.dynatrace.com/u/Romanenkov_Al3x)\
**Post date:** [September 4, 2023, 8:38am UTC](https://community.dynatrace.com/t/request-timeout-for-synthetic-monitor-in-dynatrace/22561/7 "2023-09-04T08:38:05Z")

</div>

Thanks. Helpful.
