Auto configure our log channels #1042
Merged
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.
This should allow us to simplify the logging setup in modern Laravel applications.
Instead of adding the channel manually to the
logging.php
as the first step we can configure it using only these.env
settings:We should be careful with
SENTRY_LOGS_LEVEL
in the docs since users who manually added thesentry_logs
channel will not have the boilerplate to allowSENTRY_LOGS_LEVEL
to work soLOG_LEVEL
should be prefereed, however since that usually sets the log level for the complete application it's nice to have the option to just set the Sentry version. Maybe you wantLOG_LEVEL=warning
andSENTRY_LOGS_LEVEL=debug
for example.The troubleshooting steps still apply when the application doesn't have a stack channel which has been the default for many years but not everyone keeps up to date with their config changes.