Understanding and Extending Prometheus AlertManager
summary
Adds a persistent “history” endpoint and UI tab to Alertmanager that reads past alerts from SQLite and lists every transpired alert (optionally posts to Slack); implementation modifies 6 files changed across Go, Angular, HTML and SQL, uses go-bindata to bundle static assets, and queries the alerts table (no WHERE clause in the demo). Works end-to-end on a local Prometheus+Alertmanager dev setup, hits at-least-once delivery limits, and completes in under a day as a simple prototype.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:50Prometheus AlertManager
- 3:34Purpose of AlertManager
- 5:12Routes and Receivers
- 6:20muting suppressing and correlating
- 9:16muting suppression
- 10:55notset alerts
- 12:39thirdparty alerts
- 13:09multiple destinations
- 13:58AlertManager architecture
- 15:23High availability
- 16:23History book
- 16:37Alert Manager UI
- 17:11User Story
- 18:56Sample Targets
- 19:38Prometheus Config
- 20:34Prometheus Testing
- 20:58Setting up AlertManager
- 21:31Setting up Slack Integration
- 22:21Prometheus AlertManager Visual Editor
- 22:47Build Run Test Cycle
- 23:58Test Environment
- 24:27Scraping
- 24:45Registration
- 26:44API History
- 27:10API History HTML
- 28:12Add Something New
- 28:54Resources
- 30:48Utility
related talks
23mAlerting in the Prometheus Ecosystem: The Past, Present and Future
50mMetrics and alerting with Prometheus and Grafana
01h 19mIntro + Deep Dive: Prometheus
08mPrometheus in 5 minutes
44mPrometheus in 2021 and beyond
54mPrometheus – what’s new and what’s next?
29mParanoid Observability –Success Stories and Misfortunes observing an observability stack
18mAlert Analytics