The main rabbitmq configuration file, which is usually /etc/rabbitmq/rabbitmq.config or /etc/rabbitmq/rabbitmq.conf, has log_levels commented out by default. Here is an example with Erlang format.

   %% {log_levels, [{connection, info}, {channel, info}]},

And here is an example with INI format.

# log.file.level = info

When commented out, RabbitMQ will default to log level INFO. When set to INFO, the rabbitmq log file will contain events at log levels info, warning, and error, like this.

=INFO REPORT==== 14-Oct-2020::20:51:06 ===
vm_memory_high_watermark set. Memory used:9158058968 allowed:8589934592

=WARNING REPORT==== 14-Oct-2020::20:51:06 ===
memory resource limit alarm set on node rabbit@server002.

=ERROR REPORT==== 1-Oct-2020::00:39:53 ===
** Node rabbit@server1 not responding **
** Removing (timedout) connection **

log_levels can be uncommented, to specify a certain log level. In this example, connection issue will be captured at log level DEBUG.

{log_levels, [{connection, debug}, {channel, info}]},

Or like this in the INI format.

log.file.level = debug

Following are the supported log levels.

• debug
• info
• warning
• error
• none

If you change the log level, you will need to restart the RabbitMQ server for this change to take effect.