Subscribed unsubscribe Subscribe Subscribe

Monitoring Logs

Using check-log from the official check plugin pack, you can monitor logs in Mackerel. For information on installing the official check plugin pack, you can refer to Using the official check plugin pack for check monitoring.

Using check-log

To use check-log to do log monitoring, you can, for example, append the following item in mackerel-agent.conf and then restart the mackerel-agent.

[plugin.checks.access_log]
command = "check-log --file /var/log/access.log --pattern FATAL"

Assign the target file for monitoring to the --file option, and assign the error message pattern you want to detect as a regular expression in the --pattern option. In the example above, if the character string “FATAL” appears in the targeted log file, an alert will be triggered.

Additionally, you can specify the file name of the monitoring target with regular expressions using the --file-pattern option.

The log file will be checked every minute, and any lines that have already been checked will be skipped.

If log rotation occurs, the log is read over from the beginning. To be exact, if the file size has become smaller since the previous check, it is considered a log rotation and a read-over from the beginning occurs.

Checking error output in Mackerel

By attaching the --return option to the command, error script will be outputted and its contents will be transmitted to Mackerel. When using this option, please be careful so that no concealed information gets transmitted.

Additionally, if error output is too long there is a chance it may be shortened.

Assigning a threshold and exclusion pattern for event frequency

The following option is useful in situations where if an error message appears just once it’s ok, but when frequent appearances occur you want an alert to be raised.

  • -w, --warning-over
    • a warning alert will be created if the number of error appearances exceeds the configured value
  • -c, --critical-over
    • a critical alert will be created if the number of error appearances exceeds the configured value

Additionally, by designating the --exclude option, it's possible to assign an exclusion pattern.

The following configuration, for example, will monitor the Nginx access log, and check the occurrence of 4xx and 5xx errors.

With the --exclude option we have excluded access to "robots.txt". Also, with --warning-over and --critical-over we've set it up so that if there are 3 or more occurrences within 1 minute a Warning alert will be raised, and 10 or more occurrences will result in a Critical alert.

[plugin.checks.access_status]
command = '''
  check-log                      \
    --file /var/log/nginx/access.log            \
    --pattern 'HTTP/1\.[01]" [45][0-9][0-9] '   \
    --exclude 'GET .*?robots\.txt HTTP/1\.[01]' \
    --warning-over 3 --critical-over 10         \
    --return
'''

Configuring multiple check monitors for one log

check-log saves the state of the log it read up until the previous check in the state file. The state file is saved under /var/tmp/mackerel-cache/check-log by default. If you want to configure multiple check monitors for the same log file, assign --state-dir as shown below, and save the state file in a different location.

[plugin.checks.access_status5xx]
command = '''
  check-log                     \
    --file /var/log/nginx/access.log           \
    --pattern 'HTTP/1\.[01]" 5[0-9][0-9] '     \
    --state-dir /var/mackerel-cache/check-log2
'''

For more information regarding other options, please refer to check-log --help and the README

Source code

The source code for check-log is publicly available via the URL below.

https://github.com/mackerelio/go-check-plugins/tree/master/check-log