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

Change ActiveJob log level #47

Merged
merged 2 commits into from
Sep 21, 2022
Merged

Change ActiveJob log level #47

merged 2 commits into from
Sep 21, 2022

Conversation

duncanjbrown
Copy link
Contributor

It was necessary to defer setting the logger to after ActiveJob had loaded, because ActiveJob sets a logger in its own Railtie.

https://github.com/rails/rails/blob/a5018cf149d47e1aed1e74dd35e4d519b507c364/activejob/lib/active_job/railtie.rb#L13-L15

@misaka
Copy link
Contributor

misaka commented Sep 16, 2022

Is there any value to setting the logging level to error or fatal?

@duncanjbrown
Copy link
Contributor Author

Interesting idea

@misaka
Copy link
Contributor

misaka commented Sep 16, 2022

Interesting idea

Just thinking it would still be good to see error or fatal messages. Even warning would be enough, as the noisy logging is being logged as info.

@duncanjbrown duncanjbrown changed the title Stop ActiveJob logging Change ActiveJob log level Sep 16, 2022
@duncanjbrown duncanjbrown marked this pull request as ready for review September 16, 2022 12:02
For Rails 6.0, which doesn't support this, turn of :info logging
altogether.
@duncanjbrown duncanjbrown merged commit 1ec7b35 into main Sep 21, 2022
@duncanjbrown duncanjbrown deleted the stop-logging branch September 21, 2022 10:16
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

Successfully merging this pull request may close these issues.

4 participants