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

remove MetricsLevel from TelemetrySettings #11061

Open
codeboten opened this issue Sep 5, 2024 · 2 comments
Open

remove MetricsLevel from TelemetrySettings #11061

codeboten opened this issue Sep 5, 2024 · 2 comments

Comments

@codeboten
Copy link
Contributor

A discussion on 4-Sept-2024 lead to the agreement that the struct field MetricsLevel will be removed from TelemetrySettings. This field is there to allow component authors to check a level before deciding whether to incur the cost of calculating an expensive operation.

The alternative for component authors will be to check whether an instrument is enabled or not prior to calculating the metric. This is dependent on the PR in otel go to implement this and on the spec to stabilize this feature.

The decision was that if the change would take too long to implement upstream, then we would remove this field and move any component to configure their own metric level instead. This will allow the unblocking of the component module stabilization work.

@mx-psi
Copy link
Member

mx-psi commented Sep 9, 2024

@bogdandrutu Are you going to submit any changes to the spec related to this? (Maybe related to open-telemetry/opentelemetry-specification/issues/4200?)

@mx-psi
Copy link
Member

mx-psi commented Sep 13, 2024

Given that stabilization of Enabled is not on September's release (see open-telemetry/opentelemetry-specification/pull/4204), I think we should go with the alternative plan, since mid-October would delay us significantly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Blocked
Development

No branches or pull requests

2 participants