From: Marc B. <br...@co...> - 2005-04-29 22:43:16
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Look how fast I can summarize :) 1 day! I guess the base problem presented is, 'Do I want to make a great tool (nagios) try to do something its not really designed for?' So far, the response that makes the most sense came from an private email in response; man sar. Thankyou Simon. My conclusions: Nagios is excellent at polling for, or recieving 0|1|2|3 and a < 75 char string of stuff. In order to get where I'm looking to get, I'm really looking at the 75 char stuff. Without a db, it just doesn't make much sense to write|rewrite plugins that nagios handles better (or differently than designed) for a report. I could be wrong, but I think the relationship between trapping thresholds, and reporting on the values that were used in comparison for thresholds are too different. Separating them makes is a cleaner toolset approach, and both can be nearly 100% automated, so that's a Very Good Thing. RRDtool, and APAN seem like they would provide an improvement upon the present 'top' method, but I'm restricted in the fact that I'm not going to get people to view web pages at report time. Even printing the nice graphs standalone, or cut-pasting into the existing (read: preferred format) would require manual effort, which is not my intent. I did not get a chance to peek at Cricket, as yet, but I will. I am interested in seeing how passive checks can be sent to nagios. Actually, I understand the theory, just haven't implemented any as yet. Although I do have this set of OpenVMS DEC Alpha's I haven't had much luck figuring out .. hrmmm. I don't mind using sar, or another extensible product for system value reporting|averaging (micrometrics) and using nagios for automated outage|health monitoring, alerting, and threshold trending. If I'm premature or inaccurate in my assessment, please kick me. Or shoot an email my way. Thanks again folks, - -Marc # # PGP Public Key: bru1n (at) comcast (dot) net # E8E9 FAC2 1552 DC29 7D53 FD1E 6AAE 4CA9 E5FE B976 # > -----Original Message----- > From: nag...@li... > [mailto:nag...@li...]On Behalf Of Tedman Eng > Sent: Friday, April 29, 2005 2:46 PM > To: nag...@li... > Subject: RE: [Nagios-users] Reporting > > > Cricket can be made to interface with Nagios quite easily. > > The threshold monitor in Cricket has an alerting mechanism that allows an > "exec" option which can be wired to NSCA in order to send status > to Nagios. > This is the method I chose to use, as our environment had other external > monitors that already hooked into Nagios and adding Cricket in > this way made > the most sense. > > An alternative is to use check_rrd plugin. This method polls the database > file after being collected by Cricket. > > Another alternative is to use RRDPoller, though I've no personal > experience > with this one. > http://rs.rhapsodyk.net/rrdpoller/ > > > Keeping the two different configuration schemes in sync is an issue you'll > have to address if you go with Nagios + Cricket. > > > > > -----Original Message----- > > From: Matthew Opoka [mailto:mo...@ne...] > > Sent: Friday, April 29, 2005 10:31 AM > > To: 'Marc Powell'; nag...@li... > > Subject: RE: [Nagios-users] Reporting > > > > > > > > > > Apan might suit your needs -- http://apan.sf.net/. It > > > integrates with Nagios and uses nagios' perfdata functionality. > > > > > > I personally use Cricket -- http://cricket.sf.net. I've found > > > it to be far more flexible. > > > > Does either work with 2.0? > > > > Thanks, > > > > Matthew > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. > Get your fingers limbered up and give it your best shot. 4 great events, 4 > opportunities to win big! Highest score wins.NEC IT Guy Games. Play to > win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 > _______________________________________________ > Nagios-users mailing list > Nag...@li... > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS > when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.0 (Build 1917) iQEVAwUBQnK4T2quTKnl/rl2AQjt4QgAhaF2G4Q1VJhWTk/mo2pVTbdrUFCKXNG5 ffzjuLlzcOttJ4EV1kvBfEBmarwvoflzPep2bggtbwvGBOKO81T4BJqu6wUnKpc8 1yBzLOyLu78H+2j349C+ZsOcHkwvKm4W7ejBb5pLO8uZ2joFYuqqU9ad+uP53li9 2+Kav1tVxPAyBQaSBvtUJVymLkfrMbirVB9VP8yWo15YMt7vdwGWOljKRJhULOe6 SMv9dI/ERaJP7ovUyywlzN/sbzvkllI7oPtpHH9OqaIe+9Dkrp57mxOJahndCWC8 7Rjv3y4AYdff6KdZlrAd06Tr8sHyKbrmlc9gCq/Q1hogdgUxhWbIFA== =aB8O -----END PGP SIGNATURE----- |