From gcx
Views Synthetic Monitoring check health, status, success rates, and timelines using gcx CLI commands. Lists checks, interprets OK/FAILING/NODATA, graphs trends for operators.
npx claudepluginhub grafana/gcx --plugin gcxThis skill is limited to using the following tools:
View check health, status, and timelines. Concise and direct — experienced operators need actionable status, not hand-holding.
Diagnoses Grafana Cloud Synthetic Monitoring check failures by triaging probe data, classifying failure scope, running per-probe breakdowns, and identifying root causes using gcx CLI.
Configures synthetic monitoring for uptime checks, transaction flows, and API health using Pingdom, Datadog, or New Relic. Useful for tracking app availability and performance.
Manages Better Stack uptime monitors: lists, creates, updates, pauses, deletes monitors, heartbeats, groups, and check types via API calls.
Share bugs, ideas, or general feedback.
View check health, status, and timelines. Concise and direct — experienced operators need actionable status, not hand-holding.
-o json for agent processing, default format for user displayAlways start with the full check inventory:
gcx synth checks list
Output columns: ID, JOB, TARGET, TYPE. Identify the check(s) the user is asking about.
If the user specifies a check name or target, filter after listing:
gcx synth checks list -o json | jq '.[] | select(.spec.job == "my-check")'
For all checks (overview):
gcx synth checks status
For a specific check:
gcx synth checks status <ID>
Output columns: ID, JOB, SUCCESS%, STATUS, PROBES_UP.
Status interpretation:
OK — success rate >= 50%; check is healthyFAILING — success rate < 50%; more than half of probes failing; route to synth-investigate-check for deeper analysisNODATA — no Prometheus data; check may be disabled or datasource misconfiguredShow timeline when:
FAILING statusWith a duration shorthand:
gcx synth checks timeline <ID> --since <duration>
With an explicit time range:
gcx synth checks timeline <ID> --from <start> --to <end>
Examples:
gcx synth checks timeline 42 --since 1h
gcx synth checks timeline 42 --since 6h
gcx synth checks timeline 42 --from now-24h --to now
gcx synth checks timeline 42 --from 2026-01-01T00:00:00Z --to 2026-01-02T00:00:00Z
Note: --since and --from/--to are mutually exclusive. Use one or the other.
Timeline pattern interpretation:
After presenting status:
FAILING: suggest synth-investigate-check for per-probe breakdown, failure mode classification, and PromQL deep-diveNODATA: note that no Prometheus data is available; suggest checking if the check is enabled and verifying datasource configurationsynth-manage-checksFor status overview (all checks healthy):
Checks: <N> total, <N> OK, <N> FAILING, <N> NODATA
[Table from gcx synth checks status]
All checks healthy.
For status with FAILING checks:
Checks: <N> total, <N> OK, <N> FAILING, <N> NODATA
[Table from gcx synth checks status]
FAILING checks:
- <ID> <JOB> (<TARGET>) — <SUCCESS%> success, <PROBES_UP> probes up
[Timeline graph if shown]
For per-probe breakdown and failure diagnosis, use synth-investigate-check.
For a specific check with timeline:
Check: <ID> <JOB> (<TARGET>) [<TYPE>]
Status: <OK|FAILING|NODATA>
Success: <SUCCESS%>
Probes up: <PROBES_UP>
[Timeline graph]
Timeline pattern: <flat/drops/intermittent/declining>
For NODATA checks:
Check: <ID> <JOB> (<TARGET>)
Status: NODATA — no Prometheus metrics available.
Possible causes:
- Check is disabled (spec.enabled: false)
- Synthetic Monitoring datasource not configured
- Metrics not yet available (newly created check)
Verify: gcx synth checks status <ID> -o json | jq '.spec.enabled'
gcx synth checks list returns empty: No checks configured in this context. Verify the gcx context with gcx config view.gcx synth checks status <ID> fails with "not found": Confirm the ID from gcx synth checks list. IDs are numeric.gcx synth checks timeline <ID> fails: Verify the ID exists and that the check has been running long enough to have data. New checks may show no timeline data.--since and --from/--to both provided: These flags are mutually exclusive. Use one or the other.--since 24h instead of --since 1h). The check may have been created recently.gcx config view to verify the active context. If multiple contexts exist and none specified, ask the user which to use.