Datadog Synthetics gives you a new layer of visibility on the Datadog platform. By monitoring your applications and API endpoints via simulated user requests and browser rendering, Synthetics helps you ensure uptime, identify regional issues, and track application performance. By unifying Synthetics with your metrics, traces, and logs, Datadog allows you to observe how all your systems are performing as experienced by your users.
Advanced search lets you query checks by any combination of checks attributes:
title and message - text searchstatus - Alert, No Data, OkcreatorregionmutednotificationtagsTo run a search, construct your query using the checkboxes on the left and/or the search bar along the top. The search bar updates with the equivalent query as you check the boxes. Likewise, when you modify the search bar query (or write one from scratch), the checkboxes update to reflect that change. Query results update in real-time as you edit the query; there’s no ‘Search’ button to click.
To search for specific text across all checks, titles, and notification messages, enter your text in the search bar.
Otherwise, use Boolean operators (AND, OR, and NOT) and parentheses to write complex queries using any check field:
?) is not supported, but the general wildcard (*) isFinally, the following characters are reserved: -, (, ), ", ~, *, :, ., and whitespace. To search check fields that include any of them, wrap the field string in quotes: status:("OK") AND "doc-check" is a valid query string; status:("OK") AND doc check is not.
Select Create a New check + in the upper right corner of the Synthetics page to create an API tests or a browser test. When a test fails, the endpoint is not retested: the uptime directly considers the endpoint as down.
The following metrics are generated by Synthetics checks:
synthetics.browser.* come from your browser tests.synthetics.http.* come from your API HTTP tests.synthetics.ssl.* come from your API SSL tests.| synthetics.http.response.time (gauge) | The overall time the request took to be processed. Shown as millisecond |
| synthetics.http.response.size (gauge) | The size of the response in bytes. Shown as byte |
| synthetics.http.redirect.time (gauge) | The time spent during redirections. Shown as millisecond |
| synthetics.http.dns.time (gauge) | The duration of the DNS lookup. Shown as millisecond |
| synthetics.http.connect.time (gauge) | Time to establish the TCP connection. Shown as millisecond |
| synthetics.http.ssl.time (gauge) | The duration of the TLS handshake. Shown as millisecond |
| synthetics.http.send.time (gauge) | The time to send the request. Shown as millisecond |
| synthetics.http.firstbyte.time (gauge) | The time to first byte. Shown as millisecond |
| synthetics.http.download.time (gauge) | The time to download the response. Shown as millisecond |
| synthetics.http.response (count) | The count of HTTP responses we receive. Shown as request |
| synthetics.browser.test_duration (gauge) | The test execution time. Shown as millisecond |
| synthetics.browser.time_to_interactive (gauge) | The time until the page can be interacted with. Shown as millisecond |
| synthetics.ssl.dns.time (gauge) | The duration of the DNS lookup. Shown as millisecond |
| synthetics.ssl.handshake.time (gauge) | The duration of the TLS handshake. Shown as millisecond |
| synthetics.ssl.response.time (gauge) | The overall time the request took to be processed. Shown as millisecond |
| synthetics.ssl.time_to_expiry (gauge) | The remaining time before the SSL certificate expires. Shown as minute |
| synthetics.ssl.response (count) | The count of SSL responses we receive. Shown as request |
| synthetics.api.response (count) | The count of API responses we receive. Shown as request |
