Operations → Observability
Logging
Recording structured or unstructured events from software systems for debugging and operations.
Motivation
Logging records meaningful events from a running system. It solves the problem of understanding what happened after code has already executed.
Mental model
Logs are the system diary. They should explain important decisions, failures, and state changes without requiring a debugger.
Where it fits
Logging belongs to the Operations track, inside Observability. It connects to nearby concepts through the graph relationships on this page and in the graph explorer.
Common mistakes
- Logging too much noise and hiding the signal.
- Logging secrets or personal data.
- Using logs as the only observability signal.
Related concepts
Use the metadata panel or return to the graph to explore concepts that this one requires or relates to.