CloudNative Coffee: Building Resilient Prometheus Exporters for Flaky Edge Devices
summary
A Prometheus exporter written in Go scrapes a local gaguino API and also consumes the espresso machine’s websocket HP stream, caching state so scrapes return useful data even when the device is off. It exposes an up metric, bounds requests with timeouts, defends against malformed packets, and falls back to direct scraping; it uses OpenTelemetry Collector to push per-second telemetry and runs on Kubernetes/Talos. Observed 893 shots (≈3+ per day) and the exporter stays alive under flaky conditions.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 1:11Instrumenting the espresso machine
- 3:22Building resilient exporters
- 6:34OpenTelemetry integration
- 9:23Enriching data with external sources
- 10:47Live dashboard demonstration
- 11:49Key takeaways and best practices
- 12:53Closing remarks and Q&A
related talks
40mSustainability the Container Native Way
40mBuilding a Scalable Observability Platform for Edge Compute Nodes
31mHow to Export Prometheus Metrics from Just About Anything
33mIntro: Prometheus
34mMonitor My Socks: Using Prometheus in a Polyglot Open Source Microservices
40mInstrumenting GO Applications
29m“If you Don’t Monitor your Infrastructure, you Don’t Own it!” Regain Control Thanks to Prometheus
32mDemocratizing Application Monitoring with Prometheus