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

Put channel log messages in their own log category #74

Closed
dumbbell opened this issue Mar 17, 2015 · 8 comments
Closed

Put channel log messages in their own log category #74

dumbbell opened this issue Mar 17, 2015 · 8 comments
Assignees
Milestone

Comments

@dumbbell
Copy link
Member

Reproduce what is done for connection log messages.

This should be extended to other message sources.

@dumbbell
Copy link
Member Author

The problem was reported on the mailing-list:
https://groups.google.com/d/topic/rabbitmq-users/F-Fbc7sxTrY/discussion

dumbbell added a commit that referenced this issue Mar 24, 2015
For instance, one can use the following configuration to disable
messages related to channels:
  [
    {rabbit, [
      {log_levels, [{channel, none}]}
    ]}
  ].

References #74.
@dumbbell
Copy link
Member Author

An update to the documentation on the website is ready:
rabbitmq-website@735c99268a1b619b14e45cd94b12a25dade05b1c

@dumbbell dumbbell added this to the 3.5.1 milestone Mar 24, 2015
@michaelklishin
Copy link
Member

@dumbbell perhaps you mean rabbitmq/rabbitmq-website@735c992.

@dumbbell
Copy link
Member Author

Yes, thanks!

@michaelklishin
Copy link
Member

@dumbbell is this ready for QA? I don't see a pull request for it.

@dumbbell
Copy link
Member Author

@michaelklishin, yes, it's ready.

@dumbbell
Copy link
Member Author

michaelklishin added a commit to rabbitmq/rabbitmq-website that referenced this issue Mar 26, 2015
@michaelklishin
Copy link
Member

I QA'ed this branch yesterday. Both PRs are now merged => closing.

dcorbacho added a commit that referenced this issue May 27, 2016
code_version: Acquire a lock to protect concurrent reloads
dcorbacho pushed a commit that referenced this issue Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants