You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When more than one distinct Instrument is registered with the same name for identical Meters, the implementation SHOULD emit a warning to the user informing them of duplicate registration conflict(s).
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:
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.
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: