Skip to content
atlas

Don't confuse these

Monitoring vs Observability

Why they differ

Monitoring answers questions you chose in advance; observability lets you ask new questions about problems you did not expect.

Monitoring

Observability

Watching a set of chosen measurements on systems over time and warning people when one moves outside its normal range.

Formal

The ongoing collection and display of known measures of a system's health, such as whether it answers, how busy it is and how often it fails, checked against set limits so that known kinds of trouble raise an alarm.

In plain English

Like the warning lights on a car's dashboard; they tell you quickly that the oil is low, but not why the engine is making a strange noise.

In practice

A screen in a water utility's control room shows memory use, response times and error counts for the servers that run its pumping stations, and turns red when one of them stops answering.

Why it matters

It keeps services available by catching known problems before users notice, and it is often the first place an attack shows up as odd load or failures.

Observability

Observability

How well you can work out what is going on inside a running system just from the signals it sends out.

Formal

A property of a system, reached by having it send out rich logs, metrics and traces, that lets people answer new questions about its inner state, including ones nobody thought of in advance, without changing the system.

In plain English

Like a doctor who can find out why you are ill from blood tests, scans and your own story, not just from whether you have a fever.

In practice

Checkout in a Danish web shop is slow for some customers only; by linking the traces and logs of those orders, a developer sees they all use one payment provider whose service answers slowly.

Why it matters

Modern systems fail in new and strange ways, and during an incident you need to find the cause quickly without waiting to add new checks.

Shared connections

Atlas is in beta.