synth-check-status

Inspect Synthetic Monitoring check health, status, and timelines via gcx commands.

1|Updated May 25, 2020
One-click install
npx skills add https://github.com/titaneric/dotfiles --skill synth-check-status-titaneric
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synth-check-status
Source: https://github.com/titaneric/dotfiles/tree/main/dot_agents/skills/synth-check-status
Command: npx skills add https://github.com/titaneric/dotfiles --skill synth-check-status-titaneric

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operators need a fast way to see whether their Synthetic Monitoring checks are healthy without manually querying Prometheus or navigating dashboards. This Skill surfaces check status, success rates, and failure timelines directly through gcx CLI commands. ## Core Features & Use Cases - Check Inventory and Status: List all synthetic checks and view per-check status (OK, FAILING, NODATA) with success percentages and probe counts. - Timeline Visualization: Show time-series graphs of check results over durations like 1h or 24h, or explicit time ranges, to spot drops, flapping, or gradual degradation. - Guided Routing: Directs failing checks to synth-investigate-check for per-probe diagnosis and management tasks to synth-manage-checks. - Use Case: An on-call engineer asks "are my checks healthy?" and immediately gets a status table, sees one check at 30% success, views its 6-hour timeline showing intermittent drops, and is routed to deeper investigation. ## Quick Start Ask the assistant to show the status of all synthetic monitoring checks and display a timeline for any that are failing.

Frequently Asked Questions about synth-check-status

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

FAQPage Schema
How do I check the status of synthetic monitoring checks?

Run gcx synthetic-monitoring checks status to see all checks, or add a check ID for a specific one. Output shows ID, job name, success percentage, status (OK, FAILING, NODATA), and probes up.

How do I view a synthetic check timeline over time?

Use gcx synthetic-monitoring checks timeline <ID> with either --since (e.g., 1h, 6h) or an explicit --from/--to range. The two flag styles are mutually exclusive, so pick one.

What does NODATA status mean for a synthetic check?

NODATA means no Prometheus metrics exist for the check. Common causes are a disabled check (spec.enabled: false), a misconfigured Synthetic Monitoring datasource, or a newly created check that has not produced metrics yet.

Why does the check timeline show no data for my selected range?

The check may be too new or the range too short. Try a longer duration such as --since 24h instead of --since 1h, and confirm the check ID exists via gcx synthetic-monitoring checks list.

When should I use synth-investigate-check instead of check status?

Use synth-investigate-check when a check shows FAILING status and you need per-probe breakdowns, failure mode classification, or PromQL deep-dives. The status skill only reports health and timelines, not root-cause diagnosis.