open-telemetry / open-telemetry/opentelemetry-python

Feature gap: MetricProducer

Open
#4,768 1 comment 2 reactions 1 assignee View on GitHub

@herin049 is already working on this.

Since Jul 16, 2026.

feature-request
Dominant language
Python
Stars
2.6k
Forks
1k
Avg merge
4d 15h
Merged PRs (30d)
19

Description

Is your feature request related to a problem?

We want to be able to easily read metrics from 3rd party metric sources

Describe the solution you'd like

The opentelemetry-cpp SDK contains a MetricProducer class which makes it very easy to work with 3rd party metric sources:

/**

  • MetricProducer defines the interface which bridges to third-party metric sources MUST implement,
  • so they can be plugged into an OpenTelemetry MetricReader as a source of aggregated metric data.
  • Implementations must be thread-safe, and should accept configuration for the
  • AggregationTemporality of produced metrics.
    */

https://github.com/open-telemetry/opentelemetry-cpp/blob/dbd06801eb767769a1ad427debfaf41ebb176cfa/sdk/include/opentelemetry/sdk/metrics/export/metric_producer.h#L75-L82

It'd be great if we can have this for Python as well.

Thank you!

Describe alternatives you've considered

No response

Additional Context

No response

Would you like to implement a fix?

None

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.