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
Put channel log messages in their own log category #74
Comments
The problem was reported on the mailing-list: |
For instance, one can use the following configuration to disable messages related to channels: [ {rabbit, [ {log_levels, [{channel, none}]} ]} ]. References #74.
An update to the documentation on the website is ready: |
@dumbbell perhaps you mean rabbitmq/rabbitmq-website@735c992. |
Yes, thanks! |
@dumbbell is this ready for QA? I don't see a pull request for it. |
@michaelklishin, yes, it's ready. |
Please QA the following PRs: |
I QA'ed this branch yesterday. Both PRs are now merged => closing. |
code_version: Acquire a lock to protect concurrent reloads
Position Fd at index record boundry
Reproduce what is done for connection log messages.
This should be extended to other message sources.
The text was updated successfully, but these errors were encountered: