Techment — Site Header

What is Observability

Definition

Observability is the ability to understand a system's internal state from its external outputs, achieved by collecting and correlating logs, metrics, and traces so teams can diagnose problems, understand behaviour, and answer unanticipated questions about complex systems.

« Back to Glossary Index

Reveals why systems behave as they do, not just that they failed
Correlates logs, metrics, and traces for fast root-cause analysis
Enables answering new questions without shipping new instrumentation
Reduces downtime by speeding diagnosis of complex issues

Real World Example

When a service slows intermittently, an SRE uses observability to correlate a latency metric with traces and logs, pinpointing a downstream database lock as the cause within minutes instead of guessing.

FAQs

What are the pillars of observability?

Logs, metrics, and traces, which together let teams reconstruct and understand system behaviour.

How does observability differ from monitoring?

Monitoring tracks known indicators, while observability lets you explore and answer new, unanticipated questions about system state.

Why is observability important for distributed systems?

Their complexity makes failures hard to diagnose from outputs alone, so correlating signals across services is essential.