-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Log a warning for duplicate instrument creation from the No-op Meter #3565
Comments
This is likely not what we want to do. Logging a warning would be compliant with the specification, but it would result in a poor user experience. The user that uses a no-op implementation to effectively disable OTel will still be annoyed with warnings from bad instrumentation. |
Blocked by open-telemetry/opentelemetry-specification#3071 The resolution of that issue should explicitly define the no-op implementation. Hopefully, one without logging. |
Related specification PR: open-telemetry/opentelemetry-specification#3171 |
The specification no longer requires this: open-telemetry/opentelemetry-specification#3171 |
The OpenTelemetry metric API specification states:
Currently our
noopMeter
does not do this. It needs to be updated to log a warning, similar to the SDK, to comply with the specification.The text was updated successfully, but these errors were encountered: