Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
check_logrep
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Analyses apache logs using logrep (http://code.google.com/p/wtop/).
Requires : wtop/logrep (http://code.google.com/p/wtop/) installed and configured.
Returns :
* Percentage of >399 responses in the last X minutes
* Percentage of slow (>1000msec) responses in the last X minutes
* Number of bots for the last X minutes.
* Average response time for the last X minutes.
Will go CRITICAL / WARNING only for the first 2
Returns perfdata for all.
Usage: check_logrep -w -c -W -C -G -R -M -L
OPTIONS:
-w Percentage of >399 responces WARNING threashold (%)
-c Percentage of >399 responces CRITICAL threashold (%)
-W Percentage of slow (>1000msec) responces WARNING threashold (%)
-C Percentage of slow (>1000mses) responces CRITICAL threashold (%)
-G Average responce time WARNING threashold (msec)
-R Average responce time CRITICAL threashold (msec)
-M Number of -M last minutes to report on
-L Number of lines to parse (starting from the end) This setting overrides -M. So if -L lines covers
1 minute and -M is 5, only 1 min will be reported
-h Usage, prints this message
EXAMPLE :
check_logrep -w 15 -c 20 -W 15 -C 20 -G 300 -R 500 -M 5 -L 35000
Note : You will need to do some tuning to find a suitable time (M)/no of lines(L) balance. If your -L and -M values are large and the log file is "busy" logrep will take a long time to run.
Requires : wtop/logrep (http://code.google.com/p/wtop/) installed and configured.
Returns :
* Percentage of >399 responses in the last X minutes
* Percentage of slow (>1000msec) responses in the last X minutes
* Number of bots for the last X minutes.
* Average response time for the last X minutes.
Will go CRITICAL / WARNING only for the first 2
Returns perfdata for all.
Usage: check_logrep -w -c -W -C -G -R -M -L
OPTIONS:
-w Percentage of >399 responces WARNING threashold (%)
-c Percentage of >399 responces CRITICAL threashold (%)
-W Percentage of slow (>1000msec) responces WARNING threashold (%)
-C Percentage of slow (>1000mses) responces CRITICAL threashold (%)
-G Average responce time WARNING threashold (msec)
-R Average responce time CRITICAL threashold (msec)
-M Number of -M last minutes to report on
-L Number of lines to parse (starting from the end) This setting overrides -M. So if -L lines covers
1 minute and -M is 5, only 1 min will be reported
-h Usage, prints this message
EXAMPLE :
check_logrep -w 15 -c 20 -W 15 -C 20 -G 300 -R 500 -M 5 -L 35000
Note : You will need to do some tuning to find a suitable time (M)/no of lines(L) balance. If your -L and -M values are large and the log file is "busy" logrep will take a long time to run.
Reviews (0)
Be the first to review this listing!