Add the logger config option to ease setting a PSR-3 logger to debug the SDK
#538
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This solves #370 by adding the
sentry.loggeroption which allows setting a custom PSR-3 logger to debug what's happening inside the SDK. By default the option is not set, which means that we fallback to theNullLoggerservice ID, and if it's not present we simply do nothing. I decided to not look for a service registered under thePsr\Log\LoggerInterfaceID because I don't feel safe to log internal messages to the same logger that's used by the application because those may be reported back to Sentry creating a loop.