Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bref currently only overrides the default logging channel, but in some cases, the emergency channel gets used #176

Open
j-fulbright opened this issue Feb 24, 2025 · 0 comments

Comments

@j-fulbright
Copy link
Contributor

Bref currently only overrides the default logging channel, but if a logger is missing, the emergency channel gets used and the default for the emergency channel is the laravel log, which causes errors. This happens for deprecations channel when set to null for some reason, and then throws errors in Sentry (in this case)

Causes errors..

    'deprecations' => [
        'channel' => env('LOG_DEPRECATIONS_CHANNEL', 'null'),
        'trace' => false,
    ],

due to this.

        'emergency' => [
            'path' => storage_path('logs/laravel.log'),
        ],

Image

There isnt any ENV related to it for configuration so it would require an override, but maybe it could be checked to see if it was pointing to laravel.log and if so, override.. (or add a BREF env/flag that makes it override it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant