search

prometheus / OpenMetrics

Evolving the Prometheus exposition format into a standard.
https://openmetrics.io
Apache License 2.0
2.36k stars 171 forks source link

Add a README entry on how OM relates to the wider CNCF ecosystem #137

Open tamalsaha opened 5 years ago

tamalsaha commented 5 years ago

How does this relate to OpenTelemetry ?

madan commented 5 years ago

No relation at all. In brief - OpenMetrics is we working to evolve a standard for exposing metrics OpenTelemetry is a group effort of merging OpenTracing and OpenCensus, both of which has its core around tracing.

If we get a bit deeper, OpenGTelemetry covers creation and propagation of spans, traces, metrics and so, but lacks a standard format for metric exposition (or atleast that I know of). This is where OpenMetrics comes in to define a standard around metrics exposition.

@mtwo can you help confirm the understanding, and may be add a pointer around this on the Readme.md

brian-brazil commented 5 years ago

OpenTelemetry plans to expose metrics in the OpenMetrics format, but as @mardan says the scope of the projects is different.

MacNale commented 4 years ago

Does it not make sense to merge OpenMetrics and OpenTelemetry - A standard for Metrics, Logs, and Traces?

OpenTelemetry -

image

It would be better to clarify how OpenMetrics is similar or different than OpenTelemetry project/standard in Readme.

RichiH commented 3 years ago

I will add something to the readme.

flands commented 3 years ago

How does this relate to OpenTelemetry ?

OpenTelemetry offers a reference implementation for traces and metrics today with partial support for logs (full support coming). Otel has its own wire format called OTLP. Otel is vendor-agnostic so it supports converting OTLP into another format (e.g. Jaeger or Prometheus). Given Otel supports Prometheus and does so using Prometheus libraries it supports OM.

As I understand it, OM is primarily a wire format for Prometheus today -- others could pick it up. Thus, Prometheus and OM just represent a destination for Otel to support, one of many. The only question is the feasibility of converting from OM to Otel and from Otel to OM. As it turns out, the Otel Collector and Otel Go client library both leverage prometheus/client_golang. As a result, Otel should support OM out of the box. It would be good to confirm that the translations are mapping properly, but beyond that there should be no issue today.

OpenTelemetry plans to expose metrics in the OpenMetrics format

It does today when you configure a Prometheus receiver or exporter.

Does it not make sense to merge OpenMetrics and OpenTelemetry - A standard for Metrics, Logs, and Traces?

Probably not -- OM was a standard that came out of Prometheus while OTLP is a standard that came out of OpenCensus/OpenTelemetry. Otel offers a vendor-agnostic implementation that can be extended. It was designed to support more than one standard for scenarios like this. For example, the W3C trace-context is a standard that is not part of Otel, but Otel supports.

RichiH commented 3 years ago

README not updated yet.

Please note that Datadog implemented OM support with the help of our reference implementation and no further help from us.

mhausenblas commented 3 years ago

Update: the notes from the OTel <> OpenMetrics meeting on 2020-12-02 are available

MacNale commented 3 years ago

Could not find any updates to ReadMe in this regard.