Observability
Early Observability
Summary
Observability is built into a service during design and development, before a production incident exposes a visibility gap.
Reasoning
Designing instrumentation alongside the behaviour it observes makes that behaviour diagnosable when it is released. Deferring observability until an incident leaves teams unable to explain a service at the point when that information is needed.
Implemented By These Standards
Central Operational Telemetry
Summary
Telemetry required to operate services is available through one established observability platform.
Reasoning
Distributing operational telemetry across separate service-specific systems makes incident diagnosis depend on knowing where each service stores its signals. A shared platform gives responders one place to query and correlate the telemetry required to understand behaviour across service boundaries.
Keeping operational telemetry in an established platform also applies common access, retention, and operational controls instead of requiring each team to operate a separate telemetry path.
Implemented By These Standards
Consistent Instrumentation
Summary
Instrumentation uses consistent conventions and telemetry semantics across services.
Reasoning
Common instrumentation and telemetry semantics allow signals from different services to be compared, queried, and correlated consistently. A separate approach for each service fragments operational understanding and makes cross-service diagnosis dependent on local conventions.
Implemented By These Standards
Signal Coverage
Summary
A service emits enough structured logs, metrics, and traces to explain its behaviour and dependencies without direct inspection of its running state.
Reasoning
Logs, metrics, and traces expose different aspects of service behaviour. Together they make health, performance, and individual transactions diagnosable without relying on access to a running instance.
Coverage of dependencies and integration points distinguishes a failure within the service from one caused by an external interaction.
Implemented By These Standards
- Event-Driven Messaging
- Data Access & Transaction Management
- Feature Flagging
- Managed Services
- Distributed Tracing
- Metrics, Monitoring & Alerting
- Structured Logging
- Serverless
Cross-Service Correlation
Summary
Telemetry remains correlatable across service boundaries so a transaction can be traced end to end.
Reasoning
Preserving transaction context across synchronous and asynchronous boundaries allows telemetry from each participating service to be joined into an end-to-end account of the transaction.
Implemented By These Standards
Telemetry Data Minimisation
Summary
Telemetry captures sensitive data only where observability requires it and protects any sensitive data that cannot be excluded.
Reasoning
Telemetry is retained and accessed for operational analysis, which creates exposure when it contains sensitive data. Limiting collection to necessary data reduces that exposure while preserving the information required for diagnosis.
Protecting unavoidable sensitive data reduces the possibility that telemetry reveals it beyond its intended operational use.
Implemented By These Standards
Actionable Telemetry
Summary
Telemetry remains actionable and tied to real impact, and a signal that informs no decision is not collected or alerted on.
Reasoning
Every collected signal consumes storage, processing capacity, and attention. Periodic review and removal of low-value or redundant telemetry keeps useful evidence distinguishable from routine noise and controls cost.
Tying alerts to operational or business impact directs attention towards conditions that require a response and reduces alert fatigue.
Implemented By These Standards
- Distributed Tracing
- Metrics, Monitoring & Alerting
- Observability Platform Integration
- Structured Logging
Incident Detection and Readiness
Summary
Observability detects operational issues as early as possible, and telemetry used for incident response is tested before it is needed.
Reasoning
Automated detection exposes a developing failure before reports from affected users become the primary signal. Earlier detection gives responders more time to limit impact.
Testing alerts and validating dashboards in advance provides evidence that incident telemetry is available and accurate under operational pressure.