Re: New release?
On 9/7/06, Bill Chmura <[EMAIL PROTECTED]> wrote: > > If someone wants to update the tag on the mon-client so the new stuff > that fixes mon.cgi is in, I would be more than happy to roll a few > tarballs so there could be a new release. > I'd actually already moved the tag, but was waiting for Jim to put a release out. However since he hasn't gotten to it and there is clearly demand for it, I'll at least publish a release candidate. I've placed mon and mon-client 1.2.0-RC1 files here for review: http://www.managedandmonitored.net/mon/ -David ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Starting
On 9/3/06, Toddy Prawiraharjo <[EMAIL PROTECTED]> wrote: > > > Hello all, > > I am looking for alternative to Nagios (or should i stick with it? need > opinions pls), and saw this Mon. The choice between Mon and other OSS monitoring systems like Nagios, Big Brother or any of the others is very much dependent upon your needs. My best summary of Mon is that its monitoring for sysadmins. Its not pretty, its not designed for management, its designed to allow a sysadmin to automate the performance monitoring that might otherwise be done ad-hoc or with cron jobs. It doesn't trivially provide the typical statistics gathering that many bean-counters are looking for, but its extensible and scalable in amazing ways. (See recent posts on this list about one company deploying a network of 2400 mon servers and 1200 locations, and my mon site which runs 500K monitoring tests a day, some of those on hostgroups with hundreds of hosts.) > Btw, i need some auto-monitoring tools to monitor basic unix and windows > based services, such as nfs, sendmail, smb, httpd, ftp, diskspace, etc. > I love perl so much, but then its been long time since it's been updated. Is > it still around and supported? If you love perl Mon may be perfect for you, because if there is a feature you need you can always send us a patch. :) Its definitely still around and supported. (I just posted a link to a mon 1.2.0 release candidate.) There hasn't been a lot of updates to the system in the last couple of years, but thats in part because the system is pretty stable as-is. There are certainly some big-picture changes we would like to do, but none of the current developers have had pressing reasons to work on the system. Personally, most of my original patches were based on CMU's needs when we did our Mon deployment, and since that time no major internal effort has been spent on extending the system. A review process of our monitoring systems is just starting now and that may result in either more programmer time being allocated to Mon or CMU might move away from Mon to some other system. (Obviously I'd be unhappy with that result, but I would continue to work with Mon both personally and in my consulting work.) > Any good reference on the web interface? (the > one from the site, mon.lycos.com is dead). I believe the most commonly used interface is mon.cgi, maintained by Ryan Clark, available at http://moncgi.sourceforge.net/ An older version of mon.cgi is included in the mon distribution. > And most importantly, where to > start? (any good documentation as starting point on how to use this Mon) > Start by reading the documentation, looking at the sample config file, and experimentation. A small installation can be setup in a matter of minutes. Once you've done a proof-of-concept install you can decide if Mon is right for you. -David ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: rotate Downtime log
No, Mon does not currently support this format. Using logrotate is probably an OK approach, but I suspect that you would need to restart Mon to get it to close the file and create a new one. (Haven't confirmed that, but I don't think it re-opens the file every time...) A better answer would be to add log rotation support to Mon so that at a rotation time it doesn't lose all knowledge of past failures. -David On 9/4/06, pingouin osmolateur <[EMAIL PROTECTED]> wrote: > Hi everybody > Can I use this format to rotate downtime log or > something equal? > logdir = /var/log/mon%YEAR-%MONTH > > Or is there an other solucion, i know i can use > logorate. > Thnaks in advance > ac > > > > p4.vert.ukl.yahoo.com uncompressed/chunked Mon Sep 4 16:13:33 GMT 2006 > > > ___ > Découvrez un nouveau moyen de poser toutes vos questions quelque soit le > sujet ! > Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et > vos expériences. > http://fr.answers.yahoo.com > > ___ > mon mailing list > mon@linux.kernel.org > http://linux.kernel.org/mailman/listinfo/mon > > ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
RE: Starting
>> Any good reference on the web interface? (the >> one from the site, mon.lycos.com is dead). >I believe the most commonly used interface is mon.cgi, maintained by >Ryan Clark, available at http://moncgi.sourceforge.net/ Ryan also has a website at http://www.ryanclark.org. He started working on a newer version of the mon client a while ago as well. Tim ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Starting
On Fri, 8 Sep 2006, David Nolan wrote: > My best summary of Mon is that its monitoring for sysadmins. i totally concur with david. what he said is spot-on. i will add a few things, though: the design of mon is extremely flexible, and was purposefully built the way it was in order to leverage other tools which already exist. it follows the traditional Unix design philosophy, which i think is the most elegant system design in existence to this very day. it is all about having a mechanism to connect together lots of smaller tools which do one job very well in order to solve larger problems, rather than writing a large tool for each new problem. you can also think of this design in terms of using natural language, words and grammar to phrase something you want to say. perl itself also follows this model. larry wall is a linguist (a cunning one at that, sorry couldn't resist the pun), and he applied that to perl. for example, mon leverages fping, the net-snmp tools, traceroute, rrdtool, etc. another example of mon's flexibility is how an on-call notification system with escalation was added without changing anything in mon at all, it was just a matter of writing a custom alert and plugging it in to your mon configuration file with the correct grammar. in order to get a good idea of how mon works, i would recommend reading the slides from this presentation: ftp://ftp.kernel.org/pub/software/admin/mon/mon-talk-0.4.tar.gz ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
RE : Re: rotate Downtime log
--- David Nolan <[EMAIL PROTECTED]> a écrit : > No, Mon does not currently support this format. > Using logrotate is > probably an OK approach, but I suspect that you > would need to restart > Mon to get it to close the file and create a new > one. (Haven't > confirmed that, but I don't think it re-opens the > file every time...) Thanks David I can use postrotate/endscript and prerotate/endscript to restart mon in logrotate Cheers > A better answer would be to add log rotation support > to Mon so that at > a rotation time it doesn't lose all knowledge of > past failures. > > -David > > On 9/4/06, pingouin osmolateur > <[EMAIL PROTECTED]> wrote: > > Hi everybody > > Can I use this format to rotate downtime log or > > something equal? > > logdir = /var/log/mon%YEAR-%MONTH > > > > Or is there an other solucion, i know i can use > > logorate. > > Thnaks in advance > > ac > > > > > > > > p4.vert.ukl.yahoo.com uncompressed/chunked Mon > Sep 4 16:13:33 GMT 2006 > > > > > > > ___ > > Découvrez un nouveau moyen de poser toutes vos > questions quelque soit le sujet ! > > Yahoo! Questions/Réponses pour partager vos > connaissances, vos opinions et vos expériences. > > http://fr.answers.yahoo.com > > > > ___ > > mon mailing list > > mon@linux.kernel.org > > http://linux.kernel.org/mailman/listinfo/mon > > > > > ___ Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences. http://fr.answers.yahoo.com ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Alert After not working for me...
I've recently spent a lot of time overhauling my mon.cf. I moved to m4 macros which I had been meaning to try (I recommend them to anyone who has not tried them for mon.cf). Anyway, I am trying to implement failure_interval and alertafter, but it does not seem to like it. Basically, I was thinking for a few services that are touchy to have the system regularly test every 30 minutes. But if it has a failure to test every minute. Then issue an alert if it fails 5 times in one minute. I thought it was working fine, until I did not get alerts and I realized that a blank line made mon ignore the period definitions all together. Now it complains that my: cf error: interval & alertafter not sensible. No alerts can be generated with those parameters, line 51. Now, I am guessing that it is looking at my normal interval, not my failure_interval. Would this make sense, to allow the check to consider a failure_interval if it is present? I can see that under most circumstances it does not make sense to pound something harder if it is down, but you never know... What I am doing now is just setting the alertafter to something that is crazy for the interval, but makes sense for the failure_interval ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Alert After not working for me...
On 9/8/06, Bill Chmura <[EMAIL PROTECTED]> wrote: > I've recently spent a lot of time overhauling my mon.cf. I moved to m4 > macros which I had been meaning to try (I recommend them to anyone who > has not tried them for mon.cf). > (Note to self: I really need to put together a public release of the system we use at CMU for maintaining our mon config file. It's a complete database driven web app for maintaining a large mon config...) > Basically, I was thinking for a few services that are touchy to have the > system regularly test every 30 minutes. But if it has a failure to test > every minute. Then issue an alert if it fails 5 times in one minute. Is that a typo? How can it fail 5 times in one minute if you're only testing in every minute? Since you didn't include a mon.cf snippet I'll have to guess a bit here about whats going on. I suspect you're trying to describe something like: ... interval 30m failure_interfal 10s period alertafter 5 1m I think you're trying to use the two-argument form of alertafter in a way other then the intent. The two argument form is to detect intermittent failures, i.e. 'alertafter 2 6h' would alert if a service fails twice in six hours. In the case of an intermittent failure a single failure would only result in two tests at the faster test rate before returning to the regular test rate. For what you're describing I think you want either 'alertafter 5' (i.e. 5 consecutive failures) or 'alertafter 50s' (i.e. alert when a service has failed every test for 50 seconds) -David ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
