synth-investigate-check

Diagnose synthetic monitoring check failures and identify root causes.

535|42|Updated Mar 23, 2026

Search Tags:#timeline #diagnostics #investigate #root-cause #promql #synthetic-monitoring #check-failure

Ready to run

npx skills add https://github.com/grafana/gcx --skill synth-investigate-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: synth-investigate-check
Source: https://github.com/grafana/gcx/tree/main/claude-plugin/skills/synth-investigate-check
Command: npx skills add https://github.com/grafana/gcx --skill synth-investigate-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose synthetic monitoring check failures and identify root causes.

Core Features & Use Cases

Triages probe data to classify failure scope (target down, regional/CDN, DNS, TLS, or timeout).
Performs per-probe breakdowns and timelines to map failures to regions and probes.
Guides users through gcx-based investigation steps and provides actionable next actions.

Quick Start

Run gcx synthetic-monitoring checks status to identify failures and initiate an investigation with synth-investigate-check.

Frequently Asked Questions about synth-investigate-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose synthetic monitoring check failures and identify the root cause?▼

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.

What is the best way to perform a per-probe breakdown for synthetic check failures?▼

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.

Can I use PromQL to investigate synthetic check status and regional latency timelines?▼

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.

Does synthetic monitoring triage classify failures like DNS, TLS, or timeout errors?▼

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.

Why does my synthetic check fail in specific regions but not others?▼

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.

What are the limitations of investigating synthetic check failures without per-probe data?▼

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.