Re: AW: problem in installing fping
Hello, I have found no advantage of the fping.monitor! The advantage comes when monitoring thousands hosts. -- Au revoir, 02 99 78 62 49 06 20 79 76 06 Gilles Lamiral. France, L'Hermitage (35590) 08 70 76 34 16 ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Proposal to all skilled perl developers
Hello, I'd need a new option in the configuration file to set watches and services directly to disabled when mon starts up Just write the state.d/disabled file by hand before mon starts. -- Au revoir, 02 99 78 62 49 06 20 79 76 06 Gilles Lamiral. France, L'Hermitage (35590) 08 70 76 34 16 ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: mon with MySQL backend
if anyone knows of an sql interface to mon, for storing historical logs of when devices are down and so on. Has anyone tried this, or is anyone aware of a module/interface that will allow this? Look at: http://www.linux-france.org/~glamiral/prj/dbmon/ -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06 33 (0) 8 70 76 34 16 ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: avoiding/stopping multiple alerts when upgrading a server pool
One trouble in creating one group per host/service is the shear number of groups you end up with. It is not difficult to generate a mon.cf file automaticaly with a list of hosts to be splitted, no ? If you specify 'alertafter 2 30m', service b should not alert after one failure just because service a failed one time 15 minutes ago. But service b does not since services are completely independant with their alerts. Did I misunderstand your remark ? Because of these, I would have to agree with the original poster that failures should be tracked at the service/host level, and not the group level. alertafter 2 30m 1round) A server f1 fails 1 time = no alert 2round) A server f2 fails 1 time = alert In that case you'd prefer no alert, that's it ? Since mon doesn't know what a host is, you have to write another tool, or use separate groups. -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06 http://www.sri.ucl.ac.be/SRI/frfc/rfc1855.fr.html ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: MON_LAST_* Not actually the last output...
Hello, the rationale is to show you the specifics of what was not working in the past but now is working. if the last summary / output in the upalert was from the successsful test you would not see the detail of what hostgroup members were having the problem. You would use the history list. This behavior is confusing unless your a MON admin. I remember I had to suppress it from minotaur.cgi because users think something is wrong but nothing is. They are right to think that since we all think that until we've read the mon manpage five times. -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06 http://www.sri.ucl.ac.be/SRI/frfc/rfc1855.fr.html ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: Storing performance history
Paul Socolow wrote: I know about rrdmon, but that seem to simply record whether the host was up or down, It can store per host http/smtp/nntp/ldap/... response times on rrdbases and it runs with its own scheduler. It is a mon server(s) client, but its scheduling is based on mon server(s) intervals. The last release can store on mysql databases. -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06 ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: Send a trap on non failure
David, We all read this list. Put another way, if I could call remote monitor and tell it precisely which server/hostgroup/service to check, and just have it report based on the status of that service, it would be closer to useful. Closer to hard MONconfig synchronisation. It is why remote.monitor does whole status. Use mon trap feature for doing what you want and go to hard MONconfig synchronisation :-( man mon: Traps are handled similarly to monitors: a trap sends an operational status, summary line, and description text, and mon generates an alert or upalert as necessary. -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06
Re: Send a trap on non failure
David Nolan wrote: As part of the MON deployment project I'm working on we've actually been talking about about wanting exactly this sort of thing for our multiple-mon-servers infrastructure. Use the remote.monitor -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06
Re: Website browsing
David, Though the http monitor script validate the web server is responding, it can't validate the service hosted on this webserver is correctly running .. So what is a webserver correctly running ? -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06
Re: phttp.monitor fix for uninitialized value problem
Hello, Already done. revision 1.26 date: 2000/09/27 14:58:09; author: gilles; state: Exp; lines: +2 -2 Added a rbuf default value in analyse_race() -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06
Re: Question about colors
emmanuel, I'd like to know if it's possible to configure Minotaure to display specific colors relativ to applications status. And if so, how... You can change the colors but not what they mean since it is mon server specific and minotaure is a mon client. For instance, applications in error are displayed in red, those with 'ok status' are in green. Yes. And I have a few applications whose status is in error for a while and then it turns into 'green' : I'd like this specific 'error status' to be displayed in blue for example and then in green when the status is ok. The status view is a snapshot. Good - gray (or green if another service in the same group is red) Bad - red Use the historic view to see what went wrong in the past. -- Au revoir, 33 (0) 2 99 78 62 49 Gilles Lamiral. France, L'Hermitage (35590) 33 (0) 6 20 79 76 06
setlogsock can break
Hello,
With old syslog module, setlogsock does not exist.
But the code breaks even if mon doesn't use it (solaris).
my $RCSID='$Id: mon 1.27 Sat, 08 Sep 2001 09:42:05 -0400 trockij $';
- use Sys::Syslog qw(:DEFAULT setlogsock);
+ use Sys::Syslog qw(:DEFAULT);
- ($^O eq linux || $^O eq openbsd) setlogsock ('unix');
+ ($^O eq linux || $^O eq openbsd) Sys::Syslog::setlogsock ('unix');
Thanks in advance for the next release.
--
Au revoir,
Gilles Lamiral. France, L'Hermitage (35590).
33 (0) 2 99 78 62 49
33 (0) 6 20 79 76 06
