fping.monitor output problems
the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse the output of fping correctly. (Extra info: Depending of the fping, the combination of default options used in fping.monitor works in 1.5s for the old version an 16s for the recent version.) This happens both with SUSE with fping-2.2b1-270 and Debian with fping 2.4b2-to-ipv6- # fping -e -r 3 -t 2000 -b 56 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 ICMP Host Unreachable from 192.168.140.2 for ICMP Echo sent to 192.168.140.3 192.168.140.3 is unreachable # ./fping.monitor 192.168.140.3 192.168.140.3 ICMP ICMP ICMP ICMP start time: Thu Jul 7 12:10:51 2005 end time : Thu Jul 7 12:11:07 2005 duration : 16 seconds fping args: fping -e -r 3 -t 2000 -b 56 -- unreachable hosts -- ICMP ICMP ICMP ICMP 192.168.140.3 # Kevin -- _ | Kevin Ivory | Tel: +49-551-370 |_ |\ || Service Network GmbH | Fax: +49-551-379 ._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED] Service Network | 37081 Goettingen |http://www.SerNet.de/ ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: fping.monitor output problems
On 2005-07-07 13:00, Kevin Ivory wrote: the fping.monitor included with mon-1.0.0pre5 doesn't semm to parse the output of fping correctly. ... # ./fping.monitor 192.168.140.3 192.168.140.3 ICMP ICMP ICMP ICMP some more extra information: the problematic code must have went in between pre3 and pre4: pre3's output looks fine. Kevin -- _ | Kevin Ivory | Tel: +49-551-370 |_ |\ || Service Network GmbH | Fax: +49-551-379 ._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED] Service Network | 37081 Goettingen |http://www.SerNet.de/ ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: mail.alert
Mark Lawrence wrote: Attached is (according to my tastes) a slighly clearer version of the mail alert. I think it is much clearer as well. Perhaps it can make it into the official mon, either as supplementary alternative or as the official mail.alert? Two things I noticed: 1. I hate the time stamp in the subject, but that is in the original as well. So its my personal preference. 2. The wording Affected Members is incorrect: The list given is the complete list of all hostgroup members and does not give any information which one is affected. (Hostgoup Members might be better) Kevin -- _ | Kevin Ivory | Tel: +49-551-370 |_ |\ | | Service Network GmbH | Fax: +49-551-379 ._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED] Service Network | 37081 Goettingen |http://www.SerNet.de/ ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
mail.alert
A few ideas for the mail.alert:
1. the mon description field is often more helpful than
Group/Service information. It should be included in
the mail body (depending on environment I often would
prefer to have it as a subject)
2. I have never seen the Secs until next alert filled.
(or am I doing something wrong). Can't it go away
completely.
3. It would be nice to have a configuration option
(mon.cf) to set the From: and Reply-To: headers
to some helpful value for administrative e-mail
communication.
ad 1: (just to make it easy)
# diff -u mail.alert mail.alert-patched
--- mail.alert Sat Aug 26 21:22:34 2000
+++ mail.alert-patched Wed Jun 4 18:01:50 2003
@@ -58,6 +58,7 @@
Group : $opt_g
Service : $opt_s
+Service description : $ENV{MON_DESCRIPTION}
Time noticed : $t
Secs until next alert : $opt_l
EOF
Kevin
--
_ | Kevin Ivory | Tel: +49-551-370
|_ |\ | | Service Network GmbH | Fax: +49-551-379
._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED]
Service Network | 37081 Goettingen |http://www.SerNet.de/
___
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon
Re: Alerts during exclude_period
Shchuka, Konstantin wrote: I've had to patch mon to make it process exclude_period configuration properly. Here is the diff: Thank you. That looks good. I will give it a try. Best regards, Kevin -- _ | Kevin Ivory | Tel: +49-551-3741 |_ |\ | | Service Network GmbH | Fax: +49-551-379 ._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED] Service Network | 37081 Goettingen |http://www.SerNet.de/
Alerts during exclude_period
We are getting too many false alarms, especially from services
with excluded times. The clock on the mon-server is definitely
okay. Below I have two configuration examples for services
where we still get alarms at 5:00am resp. 6:00am (the checked
services are restarted at those times). Have we got the
configuration wrong? (How to correctly debug?)
service squid
description xxx proxy
depend xxx-proxy:ping
interval 2m
monitor tcp.monitor -p 3128
period wd {Sun-Sat}
# exclude_period hr {4:55am-5:10am}
exclude_period hr {4am-6am}
alertafter 2
alertevery 12h
alert mail.alert monwatch
upalert mail.alert -u monwatch
service xxxping
description xxx ping
depend xyz-xxx:ping
interval 10m
monitor fping.monitor -r 3 -t 6000 server ;;
period wd {Sun-Sat}
exclude_period hr {5am-7am}
alertafter 2
alertevery 12h
alert mail.alert monwatch
upalert mail.alert -u monwatch
Best regards
Kevin
--
_ | Kevin Ivory | Tel: +49-551-3741
|_ |\ | | Service Network GmbH | Fax: +49-551-379
._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED]
Service Network | 37081 Goettingen |http://www.SerNet.de/
max alerts for time period
We sometimes have monitored services that go up and down several times a day. For each we correctly get alert mails upalert mails. If the rate gets too high, we would prefer to have a rate limitation on the mails (something like no more than ten mails/service/day). Is this configurable with mon? Kevin -- _ | Kevin Ivory | Tel: +49-551-3741 |_ |\ | | Service Network GmbH | Fax: +49-551-379 ._|ER | \|ET | Bahnhofsallee 1b | mailto:[EMAIL PROTECTED] Service Network | 37081 Goettingen |http://www.SerNet.de/
