-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementing a Prometheus Remote Write Exporter for Python #1302
Comments
@lzchen Can this be moved to the contrib repo since that is where we were recommended to implement the remote write exporter? |
@shovnik |
This issue was marked stale due to lack of activity. It will be closed in 30 days. |
This was done |
Hi @codeboten , I found a weird thing, the Prometheus Remote Write Exporter is only available on version v0.17b0 of opentelemetry-python-contrib. In the newer version, the module just disappeared. Is the module deprecated? If not please help to bring back it. |
@lzchen is there any future plan on providing a non experimental release? |
See open-telemetry/opentelemetry-python-contrib#933 and open-telemetry/opentelemetry-python-contrib#1359. We can only provide the non-experimental release only when the specification reaches stable https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/data-model.md#prometheus-compatibility. |
We are interested in developing a Prometheus remote write push-based exporter, sending metrics data to a Prometheus remote write integrated backend (Cortex specifically) to support exporting OTLP metrics to new endpoints without needing to run an instance of Prometheus.
This remote write exporter adds more interoperability support for the Prometheus protocol which is aligned with OpenTelemetry’s larger project goal to support Prometheus from the get go.
We plan to provide a detailed design doc, test plan and code to support this implementation. Please assign this issue to both @shovnik and @AzfaarQureshi.
cc: @alolita, @AzfaarQureshi
The text was updated successfully, but these errors were encountered: