MAAS logging (snap/2.7/CLI)

MAAS has a robust logging capability, which presents several different views, including a number of node-specific log files and several syslogd-style text logs. Each of these logs provides different information, or at the very least, different views of the same information. MAAS gathers logging information about the various MAAS states and records both automated and user-driven actions.

Five questions you may have:

  1. What is the syslog logging path?
  2. How do I use a remote syslog server?
  3. What are commissioning logs?
  4. What are test logs?
  5. What are event logs?
  6. What are audit event logs?

The discussion of these logs and their contents can be very extensive, so each type of logging has its own documentation section, reachable from the left-hand menu – or from the list of questions above.

The syslog logging path

Syslog data is kept in /var/snap/maas/common/log/rsyslog/<machine-name><yyyy-mm-dd>/messages. Every machine known to MAAS will have corresponding syslogs.

Using a remote syslog server

To add or update a remote syslog server in your MAAS environment:

maas $PROFILE maas set-config name="remote_syslog" value="$SYSLOG_FQDN"

For example, to set your syslog server to

maas $PROFILE maas set-config name="remote_syslog" value=

If you clear the remote_syslog value, MAAS will revert to the default behaviour, which is to send all syslog information to all MAAS region controllers.

For example:

maas $PROFILE maas set-config name="remote_syslog" value=""

Note that MAAS controllers’ syslogs are not forwarded to the external syslog server – only machine syslog information is forwarded.