I don't know about that. Nagios is really a roll your solution. All it really does is manage the polling intervals between checks. Just about everything else is something most people are going to write custom to their environments.
<br><br>Just make sure you limit the active checks to simple things like ping, url, and some port checking. The system health checks (like disks, cpu usage, application checks) are really best done on the host itself. Just run a cron (or whatever the windows equivilant is) job that checks the system and submits the results to the nagios server via a passive check.
<br><br>What customizations are you doing? The config files? What exactly is Nagios failing to do? <br><br><div><span class="gmail_quote">On 11/27/06, <b class="gmail_sendername">Jeff Ambrosino</b> <<a href="mailto:jbambrosino@gmail.com">
jbambrosino@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm looking for suggestions for any GPL/opensource system monitoring
<br>tools that folks can recommend.<br><br>FYI we've been using Nagios for about 6 months now with mixed results.<br> While it works, we've had to do an awful lot of customization and<br>writing our own checks (mostly application-level stuff for our
<br>proprietary software).<br><br>I think we would be alot happier with something simpler and more<br>flexible than Nagios. Right now it's a choice between further hacking<br>of Nagios vs. "roll our own" (the latter, I think, will be much more
<br>maintainable over the long run). But of course I'm looking to avoid<br>reinventing the wheel as much as possible.<br><br>Any feedback or pointers are much appreciated.<br><br>thanks,<br>JB<br><br>_______________________________________________
<br>bblisa mailing list<br><a href="mailto:bblisa@bblisa.org">bblisa@bblisa.org</a><br><a href="http://www.bblisa.org/mailman/listinfo/bblisa">http://www.bblisa.org/mailman/listinfo/bblisa</a><br></blockquote></div><br>