Finally, the
standalone CNCF OpenMetrics project archive and
move to the Prometheus project (under Prometheus governance) was completed! This means, as the Prometheus community, we can now focus on improving the protocol with the new features and learnings we got from adopting it on scale. For example:
- Adding native histogram support.
- Resolving feature discrepancy between Prometheus protobuf and OpenMetrics protobuf.
- Addressing _created lines challenges.
- OpenTelemetry compatibility e.g. suffix requirement breaking use of the Otel Semantic Convention.
- Address collision of metrics due to suffix generation.
- Adding UTF-8 support for metric and label names.
- …and more!
In the Prometheus DevSummit we initially discussed ideas for
OpenMetrics 1.1 but then more reasons for
2.0 came. As a result, we se set up a small working group for OpenMetrics 2.0 effort. In the next months we will be focusing on requirements and scope of the 2.0.
If you have any important issues with OpenMetrics 1.0 you would like to tackle in 2.0, let us know by adding an (or commenting on existing) issue , joining our Wednesday 3pm CET fortnightly meeting or pinging us on Slack! 🤗