Patrick, Sorry, it's been a long week. No hijacking here. Using SEC is already on my list, I suppose since Nagios would have a service configured to report (notification/status, etc) my question is regarding the data that will be sent to the NDO database.
Once the database is populated, reporting historical records becomes an issue. My *REAL* question is which table would be best suited for reporting? It appears to me that using the ndo_servicestatus table gets updated, rather than appended, which makes sense. I suppose using the ndo_logentries table would work best. Maybe it's time for a beer.. maybe two. Mike -----Original Message----- From: Patrick Morris [mailto:[EMAIL PROTECTED] Sent: Thursday, August 03, 2006 3:54 PM To: Mike Koponick Cc: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] NDO Services On Thu, 03 Aug 2006, Mike Koponick wrote: > Hello, > > I'm looking at implementing syslog via Nagios in a distributed > environment. I want to report historical information for network devices > that output syslog information. Of course, I will be parsing out syslog > information so I don't have a flood of traffic. I see how I can get the > data to the Nagios central server, by using something like sec.pl, which > will use the Nagios services, but when it goes to the NDO MySQL > database, I think the ndo_servicestatus table gets updated, rather than > appended to. > > Is there another way to send this type of data, and still keep a > historical data via Nagios/NDO? I suppose I could use the ndo_logentries > table, although it is very large. It sounds to me (and I could be wrong here) like you're trying to get Nagios to do something it's really not designed, or even fit, to do. Nagios is definitely *not* a syslog server. It's really good at notifying based on triggers in a log, but to actually *be* the log server? I have to wonder why you'd even try to do that when there are real logservers out there that support storing logs in databases (syslog-ng scomes to mind). You could then use sec to send status information to Nagios, and let it do what it's good at (tracking and notifying based on service states, and it would automatically save the Critical/Warning/Recovery states you sent it via NDO if you have it set up). You'd also have a real syslog server with a database back end, doing what it's good at. Trying to hijack nagios databases so you can force them to hold data they're not meant to hold just seems like a disaster in the making. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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