event broker -> SQL questions

Ben bench at silentmedia.com
Thu Oct 14 00:35:31 CEST 2004


Thanks for these so far. 

I've noticed that using your example NEB module, occasionally there are
duplicate HOST_STATUS events. Maybe identical events are supposed to be
generated by the event broker and dispatched at the same time, but I don't
know why that would be. Has anybody else seen this, and is it a bug?

On Wed, 13 Oct 2004, Titus Anderson wrote:

> > So I'm looking into how to turn event broker events into SQL statements,
> > and I have some questions about the following fields found in both
> > HOST_STATUS and SERVICE_STATUS events. I'm hoping somebody else has
> > already digested the code and can clear up my confusion. :)
> > 
> > modified_attributes appears to be redundant, because there are other
> > fields for the flags it is used to carry (active_checks_enabled,
> > notifications_enabled, etc.). Or maybe it's that those other fields are
> > redundant? Or maybe I'm just missing something?
> 
> Well, this part is easy to answer, just glancing through the code.  It appears
> that the flags are set (but never cleared) whenever an external command alters
> a field of a host or service.  For example, when you execute a
> CHANGE_NORMAL_HOST_CHECK_INTERVAL command via the external commands file, the
> MODATTR_NORMAL_CHECK_INTERVAL flag is set in the modified_attributes field for
> that host.
> 
> The rest is somewhat guesses, but here goes:
> 
> > When are these filled out, and with what?
> > event_handler - the event handler for this host or service; set at startup
> > performance_data - most recent performance data from a check; set with each
> check
> > problem_has_been_acknowledged - true or false; set if a problem has been
> acknowledged;  I presume it is cleared when the problem goes away
> > acknowledgement_type - either ACKNOWLEDGEMENT_STICKY or
> ACKNOWLEDGEMENT_NORMAL; also set when the problem is acknowledged;  don't know
> what the default value is, though
> 
> No ideas on the rest.  Haven't dug that deep yet.
>  
> > What is the logic behind these values?
> > has_been_checked
> > should_be_scheduled
> > current_notification_number
> > 
> > What are these good for?
> > failure_prediction_enabled
> > percent_state_change
> > scheduled_downtime_depth
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
> 




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl




More information about the Developers mailing list