Monitoring with Sensu 2.0
summary
Sensu 2.0 is rewritten in Go as an agent + clustered backend system using an embedded or external etcd for state and a REST API for full configuration. Agents maintain persistent WebSocket TLS connections to backends, fetch signed assets (sha512), run checks (Nagios plugins, Prometheus scrapers, statsd), and support round‑robin “one agent” checks. Demo on Kubernetes shows multi‑tenant namespaces, RBAC, sidecars and daemonsets, scaling to ten replicas, assets auto‑downloaded, Prometheus metrics stored in InfluxDB and graphed in Grafana; Slack handler fails briefly but core pipeline and storage work.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05Evolution of infrastructure
- 5:18Sensu’s origin story
- 8:53Sensu Go design
- 13:47Configuration and multi-tenancy
- 20:10Live demo introduction
- 23:01Deploying Sensu Go
- 27:11Monitoring with sidecars
- 34:40Metrics and visualization
- 39:39Kubernetes integration
- 42:19Q&A
related talks
21mChef & Sensu - Delightful Morning
33mGive yourself time to sleep
39mKeeping the lights on: Application monitoring with Sensu and BatsD
30mCloud Foundry Monitoring and Metrics Collection Using Sensu and Graphite
45mDecentralizing SaaS Monitoring Using Open-Source Tools and Standards
34mChanging the engine in flight: rebuilding monitoring at scale
22mService Monitoring Manual—2018 Edition
27mMonitoring as Code: Managing your Observability Assets the Cloud-Native Way