Statuscake vs Kibana alerting
summary
Elastic replaces external uptime checks with in-house Synthetic monitoring that triggers Kibana alerting, automating monitor deployment from a GitHub repo (cron job every five minutes) and integrating with PagerDuty and Slack. Monitors include HTTP, TCP, ICMP and real browser journeys; Kibana alerts are a few seconds slower than StatusCake, and a PagerDuty 255‑character title limit initially prevents alerts firing, forcing manual closes until switching from the rule alert ID to the alert UI ID fixes automatic resolves.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:18What is observability
- 5:29StatusCake vs Kibana alerting
- 6:33Synthetic monitoring overview
- 9:46Demo of synthetic monitors
- 13:26Kibana alerting rules
- 16:40Production challenges and fixes
- 19:53Kibana team response
- 22:02Lessons learned and next steps
- 23:29Q&A session
related talks
26mAutomating Kibana Alerting: When GitOps meets UI
27mBuilding a Scalable Monitoring System
50mApplied Alerting Philosophy
32mWho Are Your Alerts For?
23mMastering Monitoring & Alerting: Key to Seamless Performance
37mSmart Data-driven Alerts (SDdA) and How They Make DevOps Life Easier
17mMonitoring as Code
48mAlert Management as Code