-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Logging upgrade category output to stdout #4792
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
Comments
The example here folds categories and targets together. Should we start with figuring out why the upgrade category doesn't inherit the default target? I'd expect most environments to choose |
This upgrade log file was kept when RabbitMQ was switched to Lager. To support this, there is a special configuration in RabbitMQ just for this category. I would be in favor of getting rid of this legacy and treat it like other categories. It would mean that the default log file would be used out-of-the-box for upgrade logs. Perhaps there is something special with upgrades that I don't picture which is better served with a dedicated log file though. |
Prior to #4303, setting
RABBITMQ_LOGS=-
would also send the upgrade log file to stdout.We should allow using configuration entries like this:
This should also be valid for the other log files.
The text was updated successfully, but these errors were encountered: