gcx-observability

Automates end-to-end Grafana Cloud observability setup using the gcx CLI across twelve phases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up full-stack observability in Grafana Cloud involves many disconnected steps—instrumentation, SLOs, alerting, synthetic checks, load testing, on-call routing, dashboards, and cost controls—that are easy to misconfigure or skip. This Skill orchestrates the entire workflow through the gcx CLI with a test-driven approach, so every signal has a defined health contract before infrastructure is deployed. ## Core Features & Use Cases - Phased Setup Workflow: Runs 12 phases from bootstrap and discovery through instrumentation, SLO-based alerting, synthetic monitoring, k6 load testing, IRM on-call, dashboards, adaptive telemetry, GitOps export, and final review. - Test-First Definitions: Defines SLO targets, k6 thresholds, and synthetic check assertions up front (Phase 2) so later phases deploy infrastructure to satisfy them. - Parallel Execution with Verification: Uses concurrent agents for independent resources, idempotency pre-checks, and post-creation verification for every resource. - Use Case: A platform engineer onboarding a Kubernetes application to Grafana Cloud runs phases 0–11 to get Alloy collectors, SLO burn-rate alerts routed through IRM, scheduled k6 tests, and a GitOps-exported YAML tree in one guided session. ## Quick Start Ask the assistant to set up full Grafana Cloud observability for your application using the gcx-observability skill, optionally specifying phases like "0 1 2" or "all".

Frequently Asked Questions about gcx-observability

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

FAQPage Schema
How do I set up Grafana Cloud observability for a Kubernetes application?

Run the gcx-observability skill, which guides you through 12 phases: bootstrap, discovery, test definitions, Alloy instrumentation, SLO alerting, synthetic checks, k6 load tests, IRM on-call, dashboards, cost optimization, GitOps export, and review. You can run all phases or select specific ones like "0 1 2".

How do I create SLO-based burn-rate alerts in Grafana Cloud?

Phase 2 defines SLO targets per user journey in slo-*.yaml files, and Phase 4 pushes them with gcx slo definitions push, then creates 1h/6h/24h burn-rate alert rules via gcx resources push. Alerts route through contact points to Grafana IRM for escalation.

Does the skill work if some Grafana Cloud resources already exist?

Yes, every phase runs idempotency pre-checks using list commands before creating anything. Existing resources are skipped and verified, and partially completed phases resume from the first missing resource.

What container images cause problems with eBPF observability tooling?

Alpine/musl-based images break eBPF uprobe attachment and profiling, scratch/distroless images lack shared libraries and debug tools, and stripped binaries remove symbol tables. The skill scans Dockerfiles in Phase 3 and recommends debian:bookworm-slim or ubuntu:24.04 instead.

Can I export Grafana Cloud resources to Git for GitOps workflows?

Yes, Phase 10 runs gcx resources pull to export all resources as declarative YAML into a directory like ./grafana/, then verifies round-trip integrity with a dry-run push. It also generates a CI snippet to detect drift between the repo and live Grafana.