15.4. Configuring the Log Level

Every log message has a log level associated with it. The levels, in descending order, are CRITICAL, ERROR, WARNING, INFO, DEBUG, and TRACE. Red Hat Storage can be configured to generate log messages only for certain log levels. Only those messages that have log levels above or equal to the configured log level are logged.
For example, if the log level is set to info, only critical, error, warning, and info messages are logged.
The components can be configured to log at one of the following levels:
  • CRITICAL
  • ERROR
  • WARNING
  • INFO
  • DEBUG
  • TRACE

Important

Setting the log level to TRACE or DEBUG would generate excessive log messages and lead to the disks running out of memory.
To configure the log level on bricks 
#gluster volume set VOLNAME diagnostics.brick-log-level <value>

Example 15.7. Set the log level to warning on a brick

#gluster volume set testvol diagnostics.brick-log-level WARNING
To configure the syslog level on bricks 
#gluster volume set VOLNAME diagnostics.brick-sys-log-level <value>

Example 15.8. Set the syslog level to warning on a brick

#gluster volume set testvol diagnostics.brick-sys-log-level WARNING
To configure the log level on clients 
#gluster volume set VOLNAME diagnostics.client-log-level <value>

Example 15.9. Set the log level to error on a client

#gluster volume set testvol diagnostics.client-log-level ERROR
To configure the syslog level on clients 
#gluster volume set VOLNAME diagnostics.client-sys-log-level <value>

Example 15.10. Set the syslog level to error on a client

#gluster volume set testvol diagnostics.client-sys-log-level ERROR
To configure the log level on glusterd 
#glusterd --log-level <value>

Example 15.11. Set the log level to warning on glusterd

#glusterd --log-level WARNING
To configure the log level for a specific gluster command 
gluster --log-level=ERROR VOLNAME peer probe HOSTNAME

Example 15.12. Set the CLI log level to ERROR for the volume statuscommand

# gluster --log-level=ERROR volume status
Verify the log level for a specific gluster command 
#gluster --log-level ERROR volume status

See Also: