Mirrors/Munin-Contrib
1
0
Fork 0
mirror of https://github.com/munin-monitoring/contrib.git synced 2025-07-21 18:41:03 +00:00
Code Issues Releases Wiki Activity

Added extinfo to list affected logs and improved documentation

Browse source
This commit is contained in:
Kael Shipman 2018-11-18 12:26:29 -06:00
parent ac1af8bd7e
commit 6c13e1d9cf
4 changed files with 75 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

14
plugins/logs/loggrepx_
View file

@ -11,8 +11,9 @@ loggrepx - Counts the number of matching log lines by log file
=head1 DESCRIPTION
This plugin is somewhat of a bash port of the original loggrep plugin,
except that it adds a breakdown of matches per file, rather than aggregating
matches across all files.
except that it displays a breakdown of matches per file, rather than
aggregating matches across all files. It is intended to answer the
question, "Which of my logs are reporting concerning events right now?"
=head1 CONFIGURATION
@ -40,12 +41,13 @@ Available config options include the following:
env.[field]_critical - Critical level for specific logfile
NOTE: for any variable with [field] in it, [field] is derived from the
full logfile path by simply replacing all non-alphanumerics with
underscores. For example, the "warning" field for the logfile
\`/var/log/nginx/errors.log\` would be \`var_log_nginx_errors_log_warning\`
full logfile path by simply removing the preceding slash and replacing
all non-alphanumerics with underscores. For example, the "warning" field
for the logfile \`/var/log/nginx/errors.log\` would be
\`var_log_nginx_errors_log_warning\`.
One good way to get these names is to run \`munin-run [plugin-name]\`
after you've configured the required variables and then just copy/pasting
after you've configured the required variables and then just copy/paste
the names from the output.
=head1 AUTHOR