Initial commit of the Prometheus/OpenTelemetry compatibility spec #25
Conversation
This is an early draft that outlines the goals and expectations from OpenTelemetry in order to provide Prometheus support. The work is in the early stages, behavioral expectations from the collector and the libraries might change or be expanded in the future. In the long term, we will graduate this doc to the OpenTelemetry compatibility specs under the opentelemetry-specification repo.
Add more details and future work.
There was a problem hiding this comment.
I pushed a new version that removes the vague sentences and parts calling out for the lack of support/incompatibility though there is a reasonable path. The language was unnecessarily strong in a few sections and I removed them as well. The behavior expected from the collector and client libraries are categorized under the "implementation requirements" now. I think there is a challenge of trying to communicate these requirements in the context of describing compatibility/support.
@jmacd Regarding to your final question about "custom collectors", it is aligning what's proposed for the client libraries based on your code. I haven't found a clear definition of a custom collector in the Prometheus docs, and hence avoided to use it here.
This is an early draft that outlines the goals and expectations
from OpenTelemetry in order to provide Prometheus support. The
work is in the early stages, behavioral expectations from the
collector and the libraries might change or be expanded in the
future. In the long term, we will graduate this doc to the
OpenTelemetry compatibility specs under the opentelemetry-specification
repo.