What problem does it solve? When the Entity Graph shows missing services, no edges, disconnected clusters, or broken environment filtering, it is hard to tell whether the cause is absent telemetry, missing recording rules, or a label-mapping gap. This Skill provides a systematic, step-by-step diagnostic playbook using gcx commands to isolate the root cause. ## Core Features & Use Cases - Guided diagnosis workflow: Walks through stack health, entity counts, source metrics in Mimir, recording rules, edge sources, and label pipelines in a fixed order that narrows the cause. - Label-mapping gap detection: Identifies the common case where metrics carry deployment_environment but not asserts_env, causing recording rules to silently drop data. - Per-service investigation: Uses Cypher queries and PromQL checks to trace why a specific service is missing or has no edges, including service-name collision and env-scope split detection. - Use Case: A user reports "services missing from entity graph" for a specific environment. The Skill checks traces_target_info, asserts:mixin_workload_job, and the asserts_env label mapping, then pinpoints a Mimir relabeling misconfiguration and recommends the Connect Environment fix. ## Quick Start Ask the assistant to diagnose why the Entity Graph is empty or missing services for a given environment, and it will run the gcx kg diagnose workflow and report findings.
