Synthetic checks checks
The synthetics module has 9 checks. Active checks that exercise the paths that failed before — from the collector inside the VNet (private location) and, optionally, New Relic Synthetics.
This page is generated from the product's check catalog when the documentation is built, so the rules, intervals and default severities always match the version you are reading. Thresholds are defaults; entities and resources can override them.
| Check | Every | Default severity | Rule |
|---|---|---|---|
synthetics.http_endpointHTTP endpoint availability and response time | 60s | critical | warning > 2000 milliseconds · 5m / critical > 10000 milliseconds · 2m |
synthetics.tls_certificateTLS certificate validity | 3600s | warning | warning < 30 days / critical < 7 days |
synthetics.dns_resolveDNS resolution of the endpoint host | 300s | critical | warning > 500 milliseconds / critical > 2000 milliseconds |
synthetics.ag_listener_resolveListener name resolves from the collector | 120s | critical | warning > 500 milliseconds / critical > 2000 milliseconds |
synthetics.domain_authDomain authentication round trip (AADDS) | 300s | critical | ok = true |
synthetics.app_to_sqlApplication-to-SQL round trip through the listener | 60s | critical | warning > 500 milliseconds / critical > 5000 milliseconds |
synthetics.ssrs_report_renderSSRS report render test | 900s | critical | warning > 15000 milliseconds / critical > 60000 milliseconds |
synthetics.ssrs_execution_logSSRS execution log failures | 600s | warning | warning >= 1 count / critical >= 5 count |
synthetics.platform_heartbeatPlatform dead-man heartbeat | 60s | critical | critical > 5 |
Checks
synthetics.http_endpoint
HTTP endpoint availability and response time
- Measures
response_ms(milliseconds) · every60s·http- Rule
warning > 2000 milliseconds · 5m / critical > 10000 milliseconds · 2m· Default severity: critical- Action
- —
- Baseline
- Status or content mismatch is critical regardless of latency.
synthetics.tls_certificate
TLS certificate validity
- Measures
days_to_expiry(days) · every3600s·http- Rule
warning < 30 days / critical < 7 days· Default severity: warning- Action
- —
- Baseline
- Chain validity, hostname match and minimum TLS version are hard failures.
synthetics.dns_resolve
DNS resolution of the endpoint host
- Measures
resolve_ms(milliseconds) · every300s·dns- Rule
warning > 500 milliseconds / critical > 2000 milliseconds· Default severity: critical- Action
- —
- Baseline
- Resolution failure (or an unexpected address) is critical; slow resolvers are a warning.
synthetics.ag_listener_resolve
Listener name resolves from the collector
- Measures
resolve_ms(milliseconds) · every120s·dns- Rule
warning > 500 milliseconds / critical > 2000 milliseconds· Default severity: critical- Action
- Check the listener's DNS record (RegisterAllProvidersIP, TTL) and the cluster network name resource.
- Baseline
- Applications reach the group through this name; a listener that does not resolve is an outage even when every replica is healthy.
synthetics.domain_auth
Domain authentication round trip (AADDS)
- Measures
latency_ms(milliseconds) · every300s·winrm- Rule
ok = true· Default severity: critical- Action
- —
- Baseline
- This is the check that would have caught the authentication outage. Critical on first failure.
synthetics.app_to_sql
Application-to-SQL round trip through the listener
- Measures
latency_ms(milliseconds) · every60s·tsql- Rule
warning > 500 milliseconds / critical > 5000 milliseconds· Default severity: critical- Action
- —
- Baseline
- Connects to the listener name, not a node, so DNS, cluster IP and primary role are all exercised.
synthetics.ssrs_report_render
SSRS report render test
- Measures
response_ms(milliseconds) · every900s·http- Rule
warning > 15000 milliseconds / critical > 60000 milliseconds· Default severity: critical- Action
- —
- Baseline
- HTTP status other than the expected one is critical.
synthetics.ssrs_execution_log
SSRS execution log failures
- Measures
failed_executions(count) · every600s·tsql- Rule
warning >= 1 count / critical >= 5 count· Default severity: warning- Action
- —
- Baseline
- Subscriptions that fail silently show up here; group by report path.
synthetics.platform_heartbeat
Platform dead-man heartbeat
- Measures
heartbeat· every60s·http- Rule
critical > 5· Default severity: critical- Action
- —
- Baseline
- An external watcher (healthchecks-style, e.g. Uptime Kuma or Azure Monitor availability test) must alert if the platform stops pinging.
Related content
- Synthetic checks: prerequisites and how to add resources
- Thresholds and baselines: how a default threshold is overridden