Observability

General material on understanding a system from its outputs.

3Questions
11Flashcards
13Terms
Terminology

13 terms in this topic

concept

Alert Fatigue

The desensitisation that follows from alerts that are frequent, non-actionable, or not tied to user impact — after which real alerts are missed too.

tool

Application Performance Monitoring

Instrumentation inside the application that attributes latency and errors to specific code paths, queries and dependencies.

concept

Cardinality

The number of distinct time series produced by a metric, which is the product of the distinct values of all its labels — and the main driver of monit…

practice

Correlation ID

A single identifier attached to one logical operation and included in every log line it produces, anywhere in the system.

tool

Distributed Tracing

Following one logical request across every service it touches by propagating a shared trace identifier and recording timed spans.

metric

Golden Signals

The four measurements that cover most of what matters for a request-driven service: latency, traffic, errors and saturation.

practice

Health Check

An endpoint the platform polls to decide whether an instance should be restarted or should receive traffic — two different questions needing two diff…

concept

Observability

The property of being able to answer new questions about a system's internal state from its external outputs, without shipping new code.

practice

RED Method

A minimal per-service dashboard: Rate, Errors, Duration — the request-centric view of whether users are being served.

practice

Runbook

A short, actionable document telling an on-call engineer what an alert means, what to check, and what the safe mitigations are.

practice

Structured Logging

Emitting log entries as machine-parseable key-value records rather than as formatted prose.

practice

Telemetry Sampling

Keeping a subset of traces or events to bound observability cost, chosen so the ones that matter survive.

practice

USE Method

For every resource, track Utilisation, Saturation and Errors — the resource-centric complement to request-centric monitoring.

Observability

Neighbouring topics

Logging

What to log, at what level, and what must never appear in a log.

No content yet

Structured Logging

Machine-parseable events with stable names and consistent fields.

No content yet

Metrics

Counters, gauges and histograms, and percentiles rather than means.

No content yet

Cardinality

The label that multiplies series count and the bill with it.

No content yet

Distributed Tracing

Reconstructing one request's path across every service it touched.

No content yet

Correlation IDs

One identifier propagated through every hop and every log line.

No content yet

Sampling

Head-based versus tail-based, and keeping the traces that matter.

No content yet

Health Checks

Liveness versus readiness, and the check that causes the outage.

No content yet

Alerting

Symptom-based, actionable, user-impacting — and linked to a runbook.

No content yet

Alert Fatigue

How noise makes the real page invisible, and the structural fix.

No content yet

Dashboards

Answering 'is it us' in under a minute, for someone who was asleep.

No content yet

Application Performance Monitoring

Attributing latency to code paths, queries and dependencies.

No content yet

Profiling

Continuous CPU and memory attribution in production.

No content yet

Business Metrics

Orders per minute alongside error rate, because healthy is not enough.

No content yet

SLO Monitoring

Burn-rate alerting that fires on user impact rather than on thresholds.

No content yet

Log Management

Aggregation, retention tiering, search and the cost of keeping everything.

No content yet

Telemetry Cost

Observability bills that rival compute, and where to cut without going blind.

No content yet

Debugging Distributed Systems

Localising a regression when every service reports healthy.

No content yet

OpenTelemetry

Instrumenting once against an open standard rather than a vendor agent.

No content yet