Pingdom also has a simple API, so you can roll the pingdom checks into a proper nagios/zenoss check as well. This is especially helpful if you end up managing multiple sites like this.
On Sat, Dec 24, 2011 at 4:49 AM, Adam Compton <[email protected]> wrote: > On Fri, Dec 23, 2011 at 1:13 PM, Tom Perrine <[email protected]> wrote: > >> Dear monitoring gurus, >> >> What would you use for a monitoring solution for a *very* small site? >> Say no more than 3 servers, just the basic HTTP, SMTP and DNS >> services? >> >> In the "olden days" I would just do Nagios and be done, but.... >> What's the current "state of the art" in open source monitoring? >> >> I would like: >> up/down >> graphs of usage (like SMTP connections, DNS queries, disk space, etc) >> some kind of alerting (email or SMS) would be a "nice to have" >> > > I'm a big fan of Zenoss [1]; it handles monitoring and alerting, > performance counters/graphing, SNMP traps, event log collection, and > several other things, and supports both Unix and Windows servers. It also > does auto-discovery; tell it what subnets to watch and it will periodically > find and start monitoring new machines and equipment as they appear. > > They have a VMware appliance [2] to help you get up and running quickly > and easily. > > - Adam Compton > > [1]: http://community.zenoss.org/index.jspa > [2]: http://www.vmware.com/appliances/directory/155743 > > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > > -- Joseph A Kern [email protected]
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
