Add SentryLogsLogger forwarding to Sentry Structured Logs#14
Open
mSimota wants to merge 1 commit into
Open
Conversation
- New SentryLogsLogger LoggerService that forwards all levels to SentrySDK.logger with code.file/code.function/code.line attributes and parameter userInfo attached per log; tag userInfo goes to scope. - Level mapping: verbose->trace, debug->debug, info->info, warning->warn, error->error. - Does not start the SDK by default (composable next to SentryLogger, which owns SentrySDK.start); init(startingSDKWith:) for standalone use forces options.enableLogs = true. - New SentryUserIdentity helper wrapping SentrySDK.setUser so host apps do not need to link Sentry directly. - Implement missing removeUserInfo on SentryLogger. - Bump sentry-cocoa minimum to 9.0.0 (stable structured logs API). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Description
[Explain what this PR does, and why it's important.]
Changes
[List the specific changes made in this PR.]
Related Issue(s)
[If there is an existing issue related to this PR, include its number here.]
Checklist