Skip to content
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

Metrics reader supports configuring aggregation and temporality #1723

Open
kaylareopelle opened this issue Sep 6, 2024 · 1 comment
Open

Comments

@kaylareopelle
Copy link
Contributor

The metrics Reader implementation should support configuring the default aggregation and the default temporality on the basis of instrument kind. There are two lines on the spec compliance matrix about this.

This may be the relevant spec: https://opentelemetry.io/docs/specs/otel/metrics/sdk/#metricreader

Our aggregation classes set the temporality and it can be configured using an environment variable, OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE

Our instruments have a default temporality and don't have a public-facing API to change their aggregation. We should look at the configuration options for aggregation and temporality and see if they are compliant. If they are not, update the SDK to make it compliant.

Copy link
Contributor

github-actions bot commented Oct 7, 2024

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.

@github-actions github-actions bot added the stale label Oct 7, 2024
@kaylareopelle kaylareopelle added keep and removed stale labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

1 participant