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.

Sign up for GitHub

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

Jump to bottom

Support default aggregation cardinality limit when constructing MetricReader #5331

Open
CodeBlanch opened this issue Feb 8, 2024 · 0 comments
Open

Support default aggregation cardinality limit when constructing MetricReader #5331

CodeBlanch opened this issue Feb 8, 2024 · 0 comments
Labels
enhancement New feature or request metrics Metrics signal related spec-compliance Issues related to compliance with the OpenTelemetry Specification
Milestone
Future

Comments

@CodeBlanch
Copy link
Member

The OpenTelemetry SDK Specification for MetricReader says a default cardinality should be possible to specify during construction:

Status: Experimental - The default aggregation cardinality limit to use, a function of instrument kind. If not configured, a default value of 2000 SHOULD be used.

We do not currently support this in OpenTelemetry .NET.

Opening this issue for tracking. It is not something we currently plan to support as the benefit is unclear. But if this would be useful to have please comment with your use case and/or reasoning.
@CodeBlanch CodeBlanch added enhancement New feature or request metrics Metrics signal related labels Feb 8, 2024
@CodeBlanch CodeBlanch added this to the Future milestone Aug 16, 2024
@CodeBlanch CodeBlanch added the spec-compliance Issues related to compliance with the OpenTelemetry Specification label Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request metrics Metrics signal related spec-compliance Issues related to compliance with the OpenTelemetry Specification
Projects
None yet
Milestone
Future
Development

No branches or pull requests
1 participant
@CodeBlanch