Add FileDiagnosticLogger to assist with debugging the SDK
#2242
Conversation
This file contains 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
|
|
Docs PR staged here: |
bruno-garcia
approved these changes
Mar 21, 2023
|
The docs PR never got merged: getsentry/sentry-docs#6493 |
|
It will after this is released. 😉 |
|
oh I saw the message above was 2 weeks ago, assume the code was live for ages |
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.
Sometimes when debugging, I want to capture the log output to a file. Copy/paste from console isn't always possible (depending on app type), and even when it is, It could be mixed with other console output, or it could be truncated due to size of the console buffer.
This adds a
FileDiagnosticLoggerthat writes diagnostic info to the specified file. For example:Optional parameters can be used to set log level, or to write to both file and console simultaneously.