Tools / Developer tools and DevOps
Monitoring and observability
Metrics, logs, traces and alerts. Knowing your system is broken before your users tell you.
About 12 hours of study. It builds on Linux administration.
Where to learn it
Other options
- Prometheus overview (read)
Overview, then First steps
Wrong chapter, dead link, or know something better? Tell us on GitHub.
Your route to Monitoring and observability
Pick where you’re starting from. Anything your background already covers is left out, and the rest is put in order.
3 stops to go, about 40 hours of study.
Open a stop to see the book, the video course and the practice for it. Tick its circle when you've finished.
- 8 h
Programming. Ready to start.
- 20 h
Infrastructure and operations. After The shell and command-line tools.
- 12 h
Infrastructure and operations. After Linux administration.
That's the whole route to Monitoring and observability.
Which roles ask for it
- Backend engineer good to have
- DevOps / site reliability engineer in the first year
- MLOps engineer in the first year
- Platform engineer in the first year
- System administrator in the first year
- Database administrator in the first year
- Solutions architect in the first year
- Cloud engineer in the first year
- Application support engineer in the first year
What it needs and what it leads to: Monitoring and observability on the map.