Comprobaciones de pruebas sintéticas
El módulo synthetics tiene 9 comprobaciones. Pruebas activas que recorren las rutas que ya fallaron antes: desde el recolector dentro de la red virtual (ubicación privada) y, opcionalmente, con New Relic Synthetics.
Esta página se genera a partir del catálogo de comprobaciones del producto al compilar la documentación, así que las reglas, los intervalos y las severidades predeterminadas siempre coinciden con la versión que estás leyendo. Los umbrales son valores predeterminados; las entidades y los recursos pueden reemplazarlos.
| Comprobación | Cada | Severidad predeterminada | Regla |
|---|---|---|---|
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 |
Comprobaciones
synthetics.http_endpoint
HTTP endpoint availability and response time
- Mide
response_ms(milliseconds) · cada60s·http- Regla
warning > 2000 milliseconds · 5m / critical > 10000 milliseconds · 2m· Severidad predeterminada: critical- Acción
- —
- Línea base
- Status or content mismatch is critical regardless of latency.
synthetics.tls_certificate
TLS certificate validity
- Mide
days_to_expiry(days) · cada3600s·http- Regla
warning < 30 days / critical < 7 days· Severidad predeterminada: warning- Acción
- —
- Línea base
- Chain validity, hostname match and minimum TLS version are hard failures.
synthetics.dns_resolve
DNS resolution of the endpoint host
- Mide
resolve_ms(milliseconds) · cada300s·dns- Regla
warning > 500 milliseconds / critical > 2000 milliseconds· Severidad predeterminada: critical- Acción
- —
- Línea base
- Resolution failure (or an unexpected address) is critical; slow resolvers are a warning.
synthetics.ag_listener_resolve
Listener name resolves from the collector
- Mide
resolve_ms(milliseconds) · cada120s·dns- Regla
warning > 500 milliseconds / critical > 2000 milliseconds· Severidad predeterminada: critical- Acción
- Check the listener's DNS record (RegisterAllProvidersIP, TTL) and the cluster network name resource.
- Línea base
- 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)
- Mide
latency_ms(milliseconds) · cada300s·winrm- Regla
ok = true· Severidad predeterminada: critical- Acción
- —
- Línea base
- 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
- Mide
latency_ms(milliseconds) · cada60s·tsql- Regla
warning > 500 milliseconds / critical > 5000 milliseconds· Severidad predeterminada: critical- Acción
- —
- Línea base
- 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
- Mide
response_ms(milliseconds) · cada900s·http- Regla
warning > 15000 milliseconds / critical > 60000 milliseconds· Severidad predeterminada: critical- Acción
- —
- Línea base
- HTTP status other than the expected one is critical.
synthetics.ssrs_execution_log
SSRS execution log failures
- Mide
failed_executions(count) · cada600s·tsql- Regla
warning >= 1 count / critical >= 5 count· Severidad predeterminada: warning- Acción
- —
- Línea base
- Subscriptions that fail silently show up here; group by report path.
synthetics.platform_heartbeat
Platform dead-man heartbeat
- Mide
heartbeat· cada60s·http- Regla
critical > 5· Severidad predeterminada: critical- Acción
- —
- Línea base
- An external watcher (healthchecks-style, e.g. Uptime Kuma or Azure Monitor availability test) must alert if the platform stops pinging.
Contenido relacionado
- Pruebas sintéticas: requisitos previos y cómo agregar recursos
- Umbrales y líneas base: cómo se reemplaza un umbral predeterminado