How to measure and improve instrumentation quality for better full-stack observability

Grafana Cloud’s Knowledge Graph introduces an instrumentation quality report that continuously evaluates how completely and correctly each service emits and connects telemetry such as metrics, logs, traces, profiles, service graph data, and Kubernetes metadata. The report uses focused automated checks to identify issues such as missing logs or traces, malformed service names, absent Kubernetes labels, and inadequate span metrics, then converts results into percentage-based quality tiers from Poor to Perfect. By emphasizing the connections among services, dependencies, infrastructure, and diagnostic signals rather than merely the volume of data collected, it aims to prevent investigation dead ends during incidents. Fleet-wide and service-level views let teams prioritize poorly instrumented services, inspect failing and passing checks, access documentation and validation queries, filter and export results, and rerun assessments on demand. The capability requires no added setup, updates as services are discovered or changed, and is also accessible through Grafana Assistant and the gcx CLI, helping organizations identify and resolve observability gaps before they affect incident response.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.