Synthetic Monitoring
Browser monitors, HTTP monitors, synthetic locations.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HTTP Monitor default timeout value

roberto_ravo
Guide

Hello,

I've looked in the documentation but I was unable to find this kind of information: does someone know which is the default timeout value for HTTP Monitor requests?

Thanks!
Roberto

Certified Dynatrace Professional
6 REPLIES 6

AntonioSousa
DynaMight Guru
DynaMight Guru

I believe it's 10 seconds.

Antonio Sousa

Tomasz_Wozniak
Dynatrace Mentor
Dynatrace Mentor

Hi Roberto,


The default connect timeout is set to 5 seconds.
The default socket/read timeout is set to 10 seconds.


We're working on making it configurable per monitor.


Regards,
Tomek

This can now be configured per request using the 'Adapt request timeout' option. https://www.dynatrace.com/support/help/how-to-use-dynatrace/synthetic-monitoring/http-monitors/confi...

Synthetic SME and community advocate.

How do we actually apply this setting?  The documentation mentions there is an adapt request timeout, but I can't find anywhere that shows how to apply this setting.

 

I imagine it goes into the pre-request script, but I can't find what the actual property name is.  The Browser monitor script page doesn't have the word timeout anywhere in it.  I did find mention in the terraform docs for the Dynatrace provider, but I don't know if the property name they use is the exact same as the property name that the script uses, nor do I know where to put it.

By default, it's in the request object, requestTimeout. However, it's only required if you want to change from the default value. 

    "requests": [
      {
        "description": "ABC",
        "url": "https://xxx",
        "method": "GET",
        "validation": {
          "rules": [
            {
              "type": "httpStatusesList",
              "value": "<400",
              "passIfFound": true
            }
          ]
        },
        "configuration": {
          "acceptAnyCertificate": true,
          "followRedirects": true,
          "shouldNotPersistSensitiveData": false
        },
        "requestTimeout": 59
      }
    ]

This value is ignored if you're part of the HTTP Monitor Advanced settings preview. 

For the preview, requestTimeout, should be removed from the script, and instead, a customProperties added.

    "requests": [
      {
        "description": "ABC",
        "url": "https://xxx",
        "method": "GET",
        "validation": {
          "rules": [
            {
              "type": "httpStatusesList",
              "value": "<400",
              "passIfFound": true
            }
          ]
        },
        "configuration": {
          "acceptAnyCertificate": true,
          "followRedirects": true,
          "shouldNotPersistSensitiveData": false
        }
      }
    ],
    "customProperties": [
      {
        "name": "hmRequestTimeoutInMs",
        "value": "59000"
      }
    ]

 

Synthetic SME and community advocate.

Thanks for sharing this. Helpful.

Regards,

Alex Romanenkov

DT_NGINX_FORCE_UNKNOWN_VERSION_INSTRUMENTATION=1

Featured Posts