So Many Metrics, So Little Time: 5 Prometheus Exporter Best Practices
summary
Five concrete takeaways: adopt the five practices—find the right exporter, understand metrics and cardinality, set actionable golden signals—and prove them. Use promcat or GitHub stars/issues to pick exporters, add labels, store dashboard templates and configs in git, and measure alert noise vs. SLI impact. Expect tens of thousands of time series from exporters, plan retention and federation, and consider a long‑term store such as the Sysdig backend that supports promql and central dashboards.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:35Overview
- 2:45What is Prometheus
- 5:15What is an exporter
- 6:17Best Practices
- 7:06Where to Find Exporter
- 9:39How to Find a Good Exporter
- 11:13How to Analyze Metrics
- 12:52Alerting
- 14:32Actionable Alerts
- 15:53Dashboard Templates
- 18:19Enterprise Ready Access Controls
- 20:01Have a Plan for Scale
- 25:11Resources
- 26:47Free Trial
- 27:20Webinars
- 27:58Questions
- 29:14Demo Environment
- 31:55AWS Lambda Dashboard
- 33:20Cluster Overview Page
- 34:48Gold Golden Signals
- 35:50QA
related talks
24mFrom Monitoring to Observability: 10 Things to Do with Prometheus in 2020
31mHow to Export Prometheus Metrics from Just About Anything
33mPrometheus Project Intro
10mPrometheus for Monitoring Metrics - Database Monitoring Tools
35mDoing Things Prometheus Can’t Do with Prometheus
36mObservability with Prometheus and Beyond: Leveraging Cloud-native Technologies Outside of Cloud
31mEvolution of Metric Monitoring and Alerting: Upgrade Your Prometheus Today
02h 43mPrometheus from A to Z