Observability
Observability uses logs, metrics and traces to understand what a system is doing — and, after a release, whether the change caused the problem.
Logs, metrics and traces
- Logs: what happened, event by event.
- Metrics: how much and how fast, over time.
- Traces: the path of one request across services.
Service level objectives
An SLO states how reliable a service must be, for example 99.9% of requests answered in under a second. It turns monitoring into a decision: whether to ship more changes or to stabilize first.
Connecting incidents to changes
Most incidents follow a change. Knowing exactly what was deployed, when and by whom shortens the time to restore service.
How DevGob applies it
DevGob is not a monitoring tool. It complements one: it records what shipped, when and who authorized it, so an alert can be traced to the change behind it.
Read it in the documentationRelated topics
DevOps with governance, on one record
DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.