<div dir="ltr"><div><div><div><div>I vote for Zenoss Core (<a href="http://www.zenoss.org/">http://www.zenoss.org/</a>) - takes care of both performance monitoring & events/alerts, with very flexible events processing.<br>
</div>For some reason less popular in Israel when Zabbix, but has very impressive list of US customers.<br><br></div>regards,<br></div>Vitaly<br></div>PS: presented Zenoss for ILTechTalk <a href="http://www.meetup.com/ILTechTalks/events/125902492/">http://www.meetup.com/ILTechTalks/events/125902492/</a><br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 16, 2014 at 2:12 AM, Ori Berger <span dir="ltr"><<a href="mailto:linux-il@orib.net" target="_blank">linux-il@orib.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm looking for a single system that can track all of a remote server's health and performance status, and which stores a detailed every-few-seconds history. So far, I haven't found one comprehensive system that does it all; also, triggering alarms in "bad" situations (such as no disk space, etc). Things I'm interested in (in parentheses - how I track them at the moment. Note shinken is a nagios-compatible thing).<br>
<br>
Free disk space (shinken)<br>
Server load (shinken)<br>
Debian package and security updates (shinken)<br>
NTP drift (shinken)<br>
Service ping/reply time (shinken)<br>
Upload/download rates per interface (mrtg)<br>
Temperatures (sensord, hddtemp)<br>
Security logs, warning and alerts e.g. fail2ban, auth.log (rsync of log files)<br>
<br>
I have a few tens of servers to monitor, which I would like to do with one software and one console. Those servers are not all physically on the same network, nor do they have a VPN (so, no UDP) but tcp and ssh are mostly reliable even though they are low bandwidth.<br>
<br>
Please note that shinken (much like nagios) doesn't really give a good visible history of things it measures - only alerts; Also, it can't really sample things every few seconds - the lowest reasonable update interval (given shinken's architecture) is ~5 minutes for the things it measures above.<br>
<br>
Any recommendations?<br>
<br>
Thanks in advance,<br>
Ori<br>
<br>
______________________________<u></u>_________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/<u></u>mailman/listinfo/linux-il</a><br>
</blockquote></div><br></div>