Monitoring answers whether something works. Observability answers why it does not. I write about strategies for collecting logs and metrics, about alerts that do not wake people up for no reason, and about the storage costs nobody thinks about at the start.
Two hundred alerts a day means nobody reads any of them. How to design alerts so that each one requires action, and the one at three in the morning is actually worth it.
Collecting everything every second gives thousands of time series and zero answers. A small set of metrics that answers the questions „is it working” and „why not”, plus rules for storing them.
A central log system without a strategy becomes an expensive warehouse of noise. How to decide which events reach the central system, in what form, and for how long.