Skip to content

Observability

In one line

Observability lets you understand internal system state from external outputs — metrics, logs, and traces (the three pillars).

In simple words

Observability measures how well you can understand the internal state of a system from its external outputs. You can answer questions like why is this slow without adding new logging.

The three pillars: 1. Metrics — numeric data over time 2. Logs — discrete events 3. Traces — request journeys across services

Monitoring vs observability: monitoring tells you WHEN something is wrong. Observability tells you WHY. Tools: Prometheus, Grafana, Jaeger, OpenTelemetry.

Example

javascript
import { trace, metrics } from '@opentelemetry/api';
const span = tracer.startSpan('processOrder');
span.setAttribute('orderId', order.id);
// Metrics
const counter = metrics.getMeter('app').createCounter('requests');
counter.add(1, { route: '/orders' });
span.end();

OpenTelemetry instruments traces, metrics, and logs with a single API. The traceId correlates logs with traces across all services.

Common confusions

  • Confused with: Monitoring

    The difference: Monitoring tells you when something is wrong (alerts). Observability lets you explore why it is wrong. Monitoring is alerting; observability is exploration.

Related terms

Related Resources

Related Lessons

Decode error messages

Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.

View errors

← Back to glossary