Chef & Sensu - Delightful Morning
summary
Claims that Sensu 2.0 simplifies monitoring by removing external brokers and stores and exposing configuration via a backend API, demonstrates removes RabbitMQ and Redis and a real RBAC multi‑tenant model, shows a Chef cookbook that deploys a full Sensu 2.0 backend and agents with one resource, and proves assets work as tarballs (bin user lib) for plugin delivery. Three collection paths—service checks, events API, statsd—are wired to handlers like Slack and InfluxDB and a Kubernetes sidecar/daemonset deployment is shown working.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:26Sean Porter
- 3:10How Sensu Works
- 3:59Execution Scheduling for Service Checks
- 5:39Events
- 8:06Configuration Ui
- 8:25Chef Cookbook
- 10:18Three Methods of Data Collection with Sensu
- 12:03Assets
- 13:15Events Api
- 14:15Statsd
- 18:01How Is Sensu 2o Different than Sensu 1 X with Uchiwa
related talks
46mMonitoring with Sensu 2.0
33mScaling Chef Emotionally
33mGive yourself time to sleep
39mKeeping the lights on: Application monitoring with Sensu and BatsD
38mKick Starting our DevOps Transition with Chef Compliance
41mA Year with Chef and InSpec: A Retrospective with Optum
28mChef Cookbook Design Patterns
33mDeveloping for Multi-Component Environments While Keeping Your Sanity