Hi, I'm using Nagios or Zabbix as a monitoring system for my/my clients infrastructures.
When the client doesn't want an access to his monitoring system, I install Nagios with a couples of fine-tuned configuration/plugins. This is mainly a legacy position since I've been using that for years. pro: easy to get help, lots and lots of sysadmin know nagios / community very active pro: very modular pro: its nagios! con: file based, need to be reloaded to activate new config con: very bad error reporting when syntax is off. con: ugly ;-) Zabbix is the one I use when the client will request reports and access. It is "cute" and can be configured easily through a web-gui and got an agent/proxy process that can be used in active mode (the monitored-server send data back to master). Very easy to craft sql statement into monitored item (such as "time behind master") Graphic, screen and inventory management can be done through zabbix. The problem with Zabbix is that there isn't as many sysadmin that are competent with it. Certifications are available though and I know a couple sysadmin in Ottawa/Montreal/Quebec with those skills. I've seen/deployed Zabbix quite a few time with over 500 hosts each with about 30 different checks (items) and 45 triggers (limit on items). pro: cute pro: database based, new config always live. pro: easy to define "user/group" access to "servers/ressources". pro: can scale with proxy (relay system) or with a cluster of server (tree system) con: original template are not that good con: default: lots of data to your database. con: supported by a small cie (community not as active as Nagios) con: zabbix is really not that great with snmp I've also tried Zenoss and various commercial offering, but they were all "sub-quality"/"way costlier" than those 2 solutions. Pascal Charest -- Pascal Charest, skype: pascal.charest Free software consultant @ Les Laboratoires Phoenix http://www.labsphoenix.com 2009/2/27 Claudio Nanni <claudio.na...@gmail.com> > We monitor hundreds of production systems with Nagios, of any kind. > I dont have time to search for better ones, but this is doing its job. > > Cheers > > Claudio > > > 2009/2/27 Éric Fournier <eric.fourn...@cspq.gouv.qc.ca> > > > > > > > > > Hi everybody , > > > > I'm searching for a good way to monitor > MySQL > > availability (to be able to be alerted when it goes down unplanned) and i > > just wanted to poke around to know which ways you people find the most > > efficient. Are you using third party software , scripts , snmp solution > and > > so ? I'm doing my own research for this but thought if some of you had > pros > > or cons about some methods i'd be glad to hear about it. > > > > Thanks and good day > > > > *Éric Fournier* > > * > > Devez-vous vraiment imprimer ce courriel ? Pensons à l'environnement.* > > * > > Ce message est confidentiel et est à l'usage exclusif du destinataire > > identifié ci-dessus. Toute autre personne est, par les présentes, avisée > > qu'il lui est strictement interdit de le diffuser, de le distribuer, d'en > > dévoiler le contenu ou de le reproduire. Si vous avez reçu cette > > communication par erreur et que le destinataire ne peut être joint ou > vous > > est inconnu, veuillez en informer l'expéditeur par courrier électronique > > immédiatement et détruire l'original de ce message ainsi que toute > copie.* > > > > >
