| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Require an explicit Log4j2 appender opt-in before forwarding records as Sentry Logs. Preserve existing constructors and factory methods with Logs disabled by default while keeping events and breadcrumbs unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
|
Sorry, something went wrong.
📲 Install BuildsAndroid
|
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM 👍
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Stack (Logs and Metrics Enable Flags)
📜 Description
Adds a logsEnabled plugin attribute to the Log4j2 SentryAppender. The option defaults to false and requires the existing aggregate core Logs flag while that flag remains in place.
Existing public constructors and the existing createAppender factory signature remain available and delegate with Logs disabled. New overloads accept the local opt-in. Event and breadcrumb capture remain unchanged.
💡 Motivation and Context
Logging integrations need explicit local opt-ins before the aggregate core Logs flag can be removed later in this stack. Preserving existing entry points avoids an unrelated compatibility break while changing their default Logs behavior safely.
💚 How did you test it?
📝 Checklist
🔮 Next steps
Continue adding integration-local Logs opt-ins before removing the aggregate core Logs flag.