logging
Recording individual events in detail, such as one failed order, as text or structured lines.
In more detail
A log answers what happened to one specific thing and becomes expensive at high volume. Unbounded details such as user identifiers belong in logs, not metric labels. Correlate lines across services with a request identifier.
Related terms
- metric — A number measured over time, such as requests per second or error count, that shows how a system behaves in aggregate.
- distributed tracing — Following one request across every service, queue and database it touches by recording linked spans that share a trace identifier.
- correlation ID — A unique value attached to one request and passed along everywhere it goes, so its logs and traces can be found together.
Taught in
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture