Allow bref/monolog-bridge 2.0 - #77
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
bref/monolog-bridge 2.0 (brefphp/monolog-bridge#2) starts log lines with the request ID of the Lambda invocation, so that all the logs of a request can be found with it: in Bref Cloud, with
bref logs --search=<id>, or withfilter @requestId = '…'in CloudWatch Logs Insights. It is a major version because the format of the log lines changes, but the formatter's API is the same, so this bridge supports both versions.Applications get 2.0 on their next
composer update. To keep the previous log format, requirebref/monolog-bridge: ^1.0in the application'scomposer.json.This can be merged and released before bref/monolog-bridge 2.0 exists: Composer installs 1.x until then. The tests pass with the formatter of brefphp/monolog-bridge#2.