Repository navigation
histograms: Implement final OM text format #11265
Description
Activity
For reference: https://docs.google.com/document/d/1w6GhLmDYKkkNLsyPWkC3TGhW3Rs1G73j7E_nG7bhlw0/edit# enumerates ideas how an OM text format could look like
Are there any decisions made on the OM text format?
I would interested in implementing the text format for the OpenTelemetry Prometheus exporter in otel-js.
No decisions made yet. The next step would be to create a prototype in any of the instrumentation libraries based on the brainstorming doc linked above. https://github.com/prometheus/client_python comes to mind, and @csmarchbanks seemed interesting in exploring the topic. Not sure how soon he'll have time (or if he is ready to receive PRs from others).
Hello from the bug scrub.
Design doc: prometheus/proposals#32
Being worked on by @csmarchbanks @vesari
Work started to add to OM2.0: prometheus/docs#2634
We decided that this is not required to declare Native Histograms a stable feature.
Protobuf scraping has been improved to not blow up resource usage anymore (with Prometheus v3.3). Adding OM support later will not be a breaking change.
Once OM has decided how the text format representation of Native Histograms should look like (likely in OM 2.0, cf. prometheus/OpenMetrics#237 for tracking), we need to implement it here in prometheus/prometheus.
This is needed to declare Native Histograms a stable feature.See also #11172, which will inform how to design the text format.