4.7Response time
Type: response_time_ms. Checks: how long the check took, in milliseconds (ms). 1,000 ms is one second. What is timed depends on the monitor type:
| Monitor type | What is timed |
|---|---|
| URL, API | Until the response headers arrive. Downloading the body is not counted. |
| Browser (API only) | The whole run, from the first action to the last. |
| TCP | Opening the connection. |
| UDP | Until the reply arrives. |
| DNS (API only) | The lookup. |
Response time is the only assertion for TCP and UDP monitors. The dashboard labels the section assertions — response-time only for tcp (or udp). DNS monitors have no assertions in the dashboard. You can add response_time_ms to a DNS monitor through the API.
Operators: usually lt. Also gt, eq, neq.
| Type | Operator | Value | What it means |
|---|---|---|---|
response_time_ms | lt | 500 | A web page answers within half a second. |
response_time_ms | lt | 2000 | An API answers within two seconds. |
response_time_ms | lt | 50 | A TCP port opens within 50 ms. New TCP monitors start with this. |
When it fails: assertion response_time_ms < 500: got 812