Why you use Prometheus for monitoring?
summary
Describes using Prometheus because its key-value label model makes queries address specific instances by label rather than postprocessing, and because Alertmanager supports rule-based suppression so one upstream failure stops downstream duplicates. Shows configuring inhibition so a router outage suppresses per‑machine alerts, and writing custom resolvers that return true to resolve incidents or keep firing until resolved. Reports hands-on experience from a workshop and plans to adopt it for an API gateway.
AI-written summary · about
chapters (4)
related talks
08mPrometheus in 5 minutes
10mPrometheus for Monitoring Metrics - Database Monitoring Tools
31mEvolution of Metric Monitoring and Alerting: Upgrade Your Prometheus Today
40mThe Prometheus monitoring system
31mEvolving Prometheus for More Use Cases
24mFrom Monitoring to Observability: 10 Things to Do with Prometheus in 2020
29mParanoid Observability –Success Stories and Misfortunes observing an observability stack
34mPrometheus: Monitoring Microservice Applications