-
Notifications
You must be signed in to change notification settings - Fork 698
Verify previous point is returned for cumulative instruments #2773
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
Conversation
exporter/opentelemetry-exporter-prometheus/src/opentelemetry/exporter/prometheus/__init__.py
Outdated
Show resolved
Hide resolved
@srikanthccv and @aabmass could probably provide a better review. |
exporter/opentelemetry-exporter-prometheus/tests/test_prometheus_exporter.py
Outdated
Show resolved
Hide resolved
I may have forgotten what's happening here https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/aggregation.py#L139-L144. I would like another approval on this before merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this PR just to verify the behavior of Prometheus? I was thinking we should test this for the SDK's behavior, e.g. with InMemoryMetricReader and cumulative config.
Basically what Srikanth said, I'd like to know if the internals of SDK are working not just prom
exporter/opentelemetry-exporter-prometheus/src/opentelemetry/exporter/prometheus/__init__.py
Outdated
Show resolved
Hide resolved
exporter/opentelemetry-exporter-prometheus/src/opentelemetry/exporter/prometheus/__init__.py
Outdated
Show resolved
Hide resolved
Fair point, I added another test that uses |
@aabmass removed the parameters, PTAL 👍 |
Fixes #2755