Logging Level - Critical #11836
-
Using Rabbit version 3.13.1-1.el8 I have two nodes running RabbitMQ. We want to set the log level at Critical. It has been set. However, I can't seem to find a way to "break" RabbitMQ to force a critical message in the rabbit.log. I was just wondering if anyone has an idea of what constitutes a critical alert. I stopped services on one node while tailing the rabbit.log on the other node. It only reported that it lost connection to its peer as a "warning". |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
That level is not used by RabbitMQ. rabbitmqctl eval 'rabbit_log:critical("Severity = critical").'
rabbitmqctl eval 'rabbit_log:error("Severity = error").'
rabbitmqctl eval 'rabbit_log:warning("Severity = warning").' I highly recommend against disabling logging of errors, you are guaranteed to regret this decision. Use the |
Beta Was this translation helpful? Give feedback.
-
Setting log level to If the goal is to save disk space, a much better idea would be to set up logrotate. Also, |
Beta Was this translation helpful? Give feedback.
That level is not used by RabbitMQ.
rabbitmqctl eval
can be used to log a message at any level:I highly recommend against disabling logging of errors, you are guaranteed to regret this decision. Use the
error
log level or better yet, leave it atwarning
.