Metrics and alerting with Prometheus and Grafana
summary
Prometheus collects metrics by scraping /metrics (no push agent by default), stores time series in its local TSDB (15-day retention by default), and uses node_exporter, pushgateway and service discovery for targets. Grafana builds dashboards from Prometheus, while Prometheus alerting rules are routed through Alertmanager for deduplication and notification. A demo deploys an example app that triggers an alert when the alien count exceeds 20 to show end-to-end alerting.
AI-written summary · about
chapters (11)
- 0:00Session monitoring
- 1:25What is monitoring
- 10:40Prometheus ecosystem
- 17:55Prometheus architecture
- 23:08Push vs pull
- 31:17Metrics types
- 35:20Querying with PromQL
- 38:42Grafana visualization
- 40:25Alert management
- 43:30Demo: Prometheus-Grafana
- 47:16Q&A
related talks
31mEvolution of Metric Monitoring and Alerting: Upgrade Your Prometheus Today
32mDemocratizing Application Monitoring with Prometheus
02h 43mPrometheus from A to Z
08mPrometheus in 5 minutes
24mPractical Kubernetes Monitoring with Prometheus
14mFrom Metrics to Mastery: Monitoring vital signs of Kubernetes
29mParanoid Observability –Success Stories and Misfortunes observing an observability stack
23mAlerting in the Prometheus Ecosystem: The Past, Present and Future