What You Need to Know About OpenMetrics
summary
OpenMetrics is now CNCF-incubating and required by the Prometheus conformance program, and most deployments already use it: thousands of exporters, hundreds of thousands of installations and millions of users. Format changes are few but important: counters require _total, timestamps are seconds (nanosecond optional), and new metadata fields include unit and _created; text format remains mandatory and protobuf is supported. Clients (Python, Go, Java), Prometheus, Cortex, Thanos, Loki, Datadog and OpenTelemetry already interoperate and exemplars link traces to metrics for precise debugging.
AI-written summary · about
chapters (9)
- 0:00The history of metrics
- 2:18Introduction to OpenMetrics
- 5:56Adoption and compatibility
- 7:10Key breaking changes
- 8:56Improvements and features
- 12:05Exemplars in monitoring
- 13:29Current ecosystem state
- 15:00Conformance and best practices
- 17:13Future and resources
related talks
34mOpenMetrics; the State Of 1.X And the Plans For 2.0
21mImproving Monitoring Systems Interoperability with Prometheus & OpenMetrics
30mEverything you need to know about OpenMetrics 2.0!
31mEvolution of Metric Monitoring and Alerting: Upgrade Your Prometheus Today
24mLeveraging OpenTelemetry for Your Prometheus Pipeline
20mObservability and Open Telemetry
36mObservability with Prometheus and Beyond: Leveraging Cloud-native Technologies Outside of Cloud
27mThe State of Prometheus and OpenTelemetry Interoperability