What problem does it solve?
When the Grafana Entity Graph shows missing services, no edges, disconnected clusters, or broken environment filtering, finding the root cause requires checking many layers: stack onboarding, source metrics, recording rules, and label pipelines. This Skill provides a systematic, step-by-step diagnostic workflow that narrows down the cause using gcx commands.
Core Features & Use Cases
- Guided diagnosis playbook: Runs through stack health, entity counts, source metrics in Mimir, recording rules, edge source analysis, and label pipeline checks in a fixed order.
- Label mapping detection: Identifies the common gap where metrics carry
deployment_environment but not asserts_env, causing recording rules to silently drop data.
- Per-service investigation: Uses Cypher queries and PromQL to trace why a specific service is missing entities or relationships.
- Use Case: A user reports "services missing from entity graph" — the Skill runs
gcx kg diagnose, reads the Orientation block, checks traces_service_graph_request_total and asserts:relation:calls, and pinpoints a relabeling misconfiguration with a concrete fix.
Quick Start
Ask the assistant to diagnose why the Entity Graph is empty or why a specific service has no edges in your Grafana environment.
