Dash0 Synthetic Monitoring

A Dash0 synthetic check starts with an HTTP endpoint chosen by a Dash0 customer. The service requests that endpoint on a schedule from the locations assigned to the check. It tests a known URL rather than discovering pages or following links across a site.

The check definition can set the method, query parameters, headers, authentication, and request body. Assertions then evaluate details such as the response status, headers, content, or timing. Dash0's run view records the request and response so the check owner can investigate a degraded or failed result.

There is no published default user agent for these checks. Dash0 shows User-Agent: dash0-monitor in its documentation as an example of a custom header, which means that string should not be treated as a permanent product identity. Where Dash0 tracing is available, synthetic-run telemetry is a better clue than a user-agent match alone.

Dash0 documents this traffic as availability and API performance testing. It has no stated function in search indexing, AI answer retrieval, or model training. Regular requests from a Dash0 check belong in synthetic-monitoring analytics, not AI crawler reports.