Advanced settings for HTTP monitors enable you to define several timeout and size values to fine-tune HTTP monitor execution. Advanced settings are available in edit mode after HTTP monitor creation and apply to all requests in your monitor.
Turn on Enable advanced settings on the Advanced settings tab to specify custom values. If you select Use defaults > Apply, the toggle is turned off (and any custom threshold values you set up are replaced by defaults).
Hints on input format are displayed in each field. The accepted ranges and default values are displayed below each field. Defaults apply when no custom value is specified or if the advanced settings toggle is turned off.
ms, s, or min as applicable to specify units; do not use capital letters.B, kB, or MB as applicable to specify units; do not use b or KB.Field
Description
Range
Default
Input format
Request timeout
Time within which each request must be completed and the response received—this includes the time taken for DNS lookup, establishing a TCP/TLS connection, sending requests, and receiving responses.
1000 ms (1 s)–60000 ms (1 min)
10000 ms (10 s)
For example: 60000 ms, 60000ms, 60 s, 60s, 1 min, 1min
Connect timeout per request
Time within which a TCP/TLS connection for each request must be established—in the case of HTTPS requests, this includes the TLS handshake, negotiating a cipher with the server, analyzing certificates, and all other parts of the TLS protocol.
1000 ms (1 s)–60000 ms (1 min)
5000 ms (5 s)
For example: 60000 ms, 60000ms, 60 s, 60s, 1 min, 1min
Monitor execution timeout
Time within which monitor execution must be completed—this is the response time for the sum of all requests.
10000 ms (10 s)–300000 ms (5 min)
60000 ms (60 s)
For example: 60000 ms, 60000ms, 60 s, 60s, 1 min, 1min
Pre- or post-execution script timeout
Maximum duration of a request's pre-execution or post-execution script
1000 ms (1 s)–10000 ms (10 s)
1000 ms (1 s)
For example: 1000 ms, 1000ms, 1 s, 1s
DNS query timeout per request
Maximum duration of a DNS lookup for resolving a hostname for each request
Make sure that the DNS query timeout per request is not greater than the request timeout divided by the number of DNS servers. If a DNS query times out against one server, the Synthetic engine queries other available servers.
For example, if the request timeout is 30 s and there are three DNS servers, the DNS timeout should not be greater than 30 / 3 = 10 s.
1000 ms (1 s)–60000 ms (1 min)
5000 ms (5 s)
For example: 60000 ms, 60000ms, 60 s, 60s, 1 min, 1min
Maximum size of each request header
Maximum number of bytes per HTTP request header—if a header is larger, it is truncated.
10240 B (10 kB)–61440 B (60 kB)
50000 B
For example: 10240 B, 10240B, 10 kB, 10kB
Maximum request body size
Maximum number of bytes for an HTTP POST payload (request body)—if the payload is larger, it is truncated.
10240 B (10 kB)–102400 B (100 kB)
50000 B
For example: 10240 B, 10240B, 10 kB, 10kB
Maximum size of each pre-execution or post-execution script
Maximum number of bytes per pre-execution or post-execution script—if a script is larger, it is truncated before execution.
10240 B (10 kB)–102400 B (100 kB)
50000 B
For example: 10240 B, 10240B, 10 kB, 10kB
Maximum size of response body read by post-execution scripts
The maximum number of bytes of the content of a response passed to a post-execution script (cannot be greater than maximum response body size)—if the response body is larger, it is truncated before being passed to the script.
10240 B (10 kB)–1048576 B (1 MB)
50000 B
For example: 10240 B, 10240B, 10 kB, 10kB
Maximum response body size
Maximum size of the response body read by the Synthetic engine for string/regex validation (cannot be less than the maximum size of the response body read by post-execution scripts)
51200 B (50 kB)–20971520 B (20 MB)
10485760 B
For example: 1048576 B, 1048576B, 1024 kB, 1024kB, 1 MB, 1MB