Research
Observability as a Queryable System
Treating operational telemetry as a system that should answer questions directly, not only populate dashboards after the fact.
Question
What changes when observability data is designed for direct technical investigation instead of passive dashboard consumption?
Context
Teams often have logs, metrics, traces, and events, yet still struggle to answer basic operational questions quickly. The bottleneck is frequently retrieval design rather than collection volume.
Experiment
Current work examines query surfaces, MCP-style access patterns, schema consistency, and the practical tradeoffs between dashboards, search systems, and structured investigation workflows.
Findings
Early evidence suggests that consistent naming, bounded cardinality, and cross-source queryability matter more than adding additional visualization layers.
Related Notes
Record
This research focuses on operator usefulness.
Questions in scope:
- Which operational questions deserve first-class query paths?
- How much telemetry structure is enough before dashboards become secondary?
- Where do logs, traces, and system metadata need shared vocabulary?