Providing Monitoring Result Data to Chef
summary
A small library called Prometheus metrics cookbook queries Prometheus via the built‑in HTTPClient (no extra gems) and exposes a current_cluster_health routine that returns a scalar timestamp/value. Recipe code uses that value at compile time to skip risky actions (deploys) if under 50% healthy, and treats Prometheus being unreachable as “proceed” by default. The implementation avoids bulk data bags and per-node plugins, keeps queries focused, and the demo code successfully gates deployments without adding new agents or constant chef runs.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:34Common Infrastructure Architecture
- 3:02Monitoring Systems
- 6:04Metrics
- 10:29Monitoring vs Configuration Management
- 14:30Delayed Action
- 17:54Data Bags
- 21:17Prometheus Metrics Spec
- 24:01JSON Client
- 27:56Example
- 29:07Monitoring API
- 30:00Hiring
- 30:22Questions
related talks
29m“If you Don’t Monitor your Infrastructure, you Don’t Own it!” Regain Control Thanks to Prometheus
32mDemocratizing Application Monitoring with Prometheus
10mPrometheus for Monitoring Metrics - Database Monitoring Tools
40mThe Prometheus monitoring system
27mPrometheus: The Unsung Heroes
16mPrometheus 101
24mPractical Kubernetes Monitoring with Prometheus
08mPrometheus in 5 minutes