2d00f7b7ba
Log lines can get quite large, as we previously noticed with rsync error log lines. We added a setting to cap those, but it really looks like we should have just done this overall limit. We noticed the issue when we switched to UDP syslogging and it would occasionally blow past the 16436 lo MTU! This causes Python's logging code to get an error and hilarity ensues. Change-Id: I44bdbe68babd58da58c14360379e8fef8a6b75f7
26 lines
815 B
Plaintext
26 lines
815 B
Plaintext
[drive-audit]
|
|
# device_dir = /srv/node
|
|
# log_facility = LOG_LOCAL0
|
|
# log_level = INFO
|
|
# log_address = /dev/log
|
|
# The following caps the length of log lines to the value given; no limit if
|
|
# set to 0, the default.
|
|
# log_max_line_length = 0
|
|
# minutes = 60
|
|
# error_limit = 1
|
|
#
|
|
# Location of the log file with globbing
|
|
# pattern to check against device errors.
|
|
# log_file_pattern = /var/log/kern*
|
|
#
|
|
# Regular expression patterns to be used to locate
|
|
# device blocks with errors in the log file. Currently
|
|
# the default ones are as follows:
|
|
# \berror\b.*\b(sd[a-z]{1,2}\d?)\b
|
|
# \b(sd[a-z]{1,2}\d?)\b.*\berror\b
|
|
# One can overwrite the default ones by providing
|
|
# new expressions using the format below:
|
|
# Format: regex_pattern_X = regex_expression
|
|
# Example:
|
|
# regex_pattern_1 = \berror\b.*\b(dm-[0-9]{1,2}\d?)\b
|