open-telemetry / open-telemetry/opentelemetry-ruby
Metrics reader supports configuring aggregation and temporality
@zvkemp is already working on this.
Since Dec 12, 2024.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.