Attach Laravel's Context to events as metadata #537
Merged
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
imjoehaines
force-pushed
the
laravel-11-context
branch
from
554ddb6 to
707df40
Compare
imjoehaines
force-pushed
the
laravel-11-context
branch
from
707df40 to
28e190b
Compare
tomlongridge
approved these changes
May 23, 2024
Merged
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.
Goal
Laravel 11 added a new
Contextfeature that allows adding arbitrary metadata to its logging systemThis PR adds support for reading from the
Contextand attaching it to events as metadataThere is a new configuration option,
attach_hidden_context(or environment variableBUGSNAG_ATTACH_HIDDEN_CONTEXT), that controls whether "hidden context" is added as metadata as well. This is disabled by default to avoid accidentally leaking dataSee also #536 & https://laravel.com/docs/11.x/context