Improve error logging #177
Merged
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
By logging the exception on the context various logging tools can generate a stack trace
Contributor
|
Hello @mrtus, thank you for the contribution. We will review this and get back to you after that. Filed Internally as 209083. |
Merged
LaunchDarklyReleaseBot
added a commit
that referenced
this pull request
Jul 12, 2023
## [5.1.1] - 2023-07-11 ### Changed: - Invalid context log message now includes the flag key as part of the Psr\Log context. (Thanks, [mrtus](#179)!) - Error logging now includes the exception in the Psr\Log exception context key. (Thanks, [mrtus](#177)!) --------- Co-authored-by: Eli Bishop <[email protected]> Co-authored-by: hroederld <[email protected]> Co-authored-by: LaunchDarklyCI <[email protected]> Co-authored-by: Ben Woskow <[email protected]> Co-authored-by: Ben Woskow <[email protected]> Co-authored-by: Gavin Whelan <[email protected]> Co-authored-by: elliot <[email protected]> Co-authored-by: Elliot Haisley <[email protected]> Co-authored-by: Harpo Roeder <[email protected]> Co-authored-by: LaunchDarklyReleaseBot <[email protected]> Co-authored-by: Ember Stevens <[email protected]> Co-authored-by: ember-stevens <[email protected]> Co-authored-by: Matthew M. Keeler <[email protected]> Co-authored-by: charukiewicz <[email protected]> Co-authored-by: Joey Malinowski <[email protected]> Co-authored-by: Christian Charukiewicz <[email protected]> Co-authored-by: Matthew M. Keeler <[email protected]> Co-authored-by: Colin Henwood <[email protected]> Co-authored-by: Colin Henwood <[email protected]> Co-authored-by: Eli Bishop <[email protected]> Co-authored-by: Louis Chan <[email protected]> Co-authored-by: ld-repository-standards[bot] <113625520+ld-repository-standards[bot]@users.noreply.github.com> Co-authored-by: Kane Parkinson <[email protected]> Co-authored-by: Michiel Devriese <[email protected]>
Member
|
Released in 5.1.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Requirements
Describe the solution you've provided
Various logging tools can generate a stack trace based on the exception being on the 'exception' key in the logging context. See PSR-3
Describe alternatives you've considered
We could keep the
debuglog but since this introduces duplicate logging and does not provide a browsable context of the exception, it is better to remove this.I am a bit conflicted about keeping
$e->getMessage()as part of the error message, since this becomes redundant with the same reason as before, many logging tools simply use the exception on the logging context already and use it as a message.