synth-investigate-check

To diagnose synthetic monitoring check failures, you can triage probe data to classify the failure scope, such as target down, DNS, TLS, or timeout issues. This process maps failures to specific regions and probes to identify the root cause quickly.

Performing a per-probe breakdown for synthetic check failures involves analyzing regional latency timelines and probe data. This isolates regional or CDN issues, mapping exactly which probes are failing and classifying the underlying network or target problem.

Yes, you can use PromQL to query synthetic monitoring metrics for investigating check status and regional latency timelines. Analyzing these queries helps map failures to regions and provides actionable next steps for resolution.

Yes, synthetic monitoring triage classifies failure scopes including target down, regional/CDN, DNS, TLS, and timeout errors. It guides users through investigation steps to categorize the issue and determine actionable next actions.

Synthetic check failures in specific regions often indicate regional or CDN issues rather than a target down scenario. By performing a per-probe breakdown and analyzing regional latency timelines, you can isolate the affected probes and confirm the root cause.

Investigating synthetic check failures without per-probe data limits your ability to map failures to specific regions and classify the failure scope accurately. You need probe breakdowns to distinguish between target down, regional, DNS, or timeout issues effectively.