feat(metrics): add MetricProducer support (fixes #4768) #4770
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Prhmma
force-pushed
the
feature/4768-metric-producer
branch
from
fec8ce1 to
b66924f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Introduces a
MetricProducerinterface and integrates the producer collection intoMetricReader.collect, enabling the Python SDK to ingest metrics from third-party sources. Adds supporting tests, documentation, and examples.Fixes #4768
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
tox -e py310-test-opentelemetry-sdk -- -k "MetricProducer" -vv (uses uv to provision; passes MetricProducer suite, with the known benign Windows teardown AttributeError in TestLoggingInit.test_dictConfig_preserves_otel_handler)
Does This PR Require a Contrib Repo Change?
Checklist: