-
Notifications
You must be signed in to change notification settings - Fork 821
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
NoopLogger #1523
Comments
Logging is an implementation detail of the SDK. The API has no bearing on it. The SDK internals could be changed to have different logging levels or behaviors with no difference in the public API. |
but then we keep other noop implementations in api. Simple example: To avoid duplications if I want to implement a new plugin or anything else based only on api, I cannot define a default NoopLogger without using SDK, and because it is not in api I will have to import nooplogger from sdk or create a new one. This is jsut wrong and imho api should provide a default implementation for that. |
Is this fixed? I see #1540 actually exports the When registering a |
@obecny looks like we have a NoopLogger in the API and SDK. I'm going to close this, but open a new issue to remove the core NoopLogger |
* chore: extract sql commenting logic to common package * feat(instrumentation-mysql2): sqlcommenter support * fix(instrumentation-mysql2): properly assign commented sql * chore(instrumentation-mysql2): test sqlcommenter * chore(instrumentation-mysql2): update readme with new option * chore: revert workflows autoformat * chore(sql-common): specify api devDep * chore: update release-please manifests * chore(sql-common): fix copy pasted readme * fix(instrumentation-mysql2): proper test cleanup logic * fix(instrumentation-mysql2): proper test config handling --------- Co-authored-by: Haddas Bronfman <[email protected]>
Should we move the
NoopLogger
from core to api as we have with other noop implementations ?The text was updated successfully, but these errors were encountered: