James King wrote:
> Hello all,
>
> I'm attempting to write a NEB module that will enable forwarding of
> service state transitions to another NMS platform. I'm registering
> for NEBCALLBACK_SERVICE_STATUS_DATA, but my callback is being invoked
> twice for each status update, with identical timestamp, type code and
> identical current_state and last_state in the (service *)
> (data->object_ptr). There's only a single event type associated with
> this hook (NEBTYPE_SERVICESTATUS_UPDATE). Is this normal behavior for
> this hook (and if so, what is the reasoning behind this, or is there
> at least a difference between the 2 invocations that I can use to
> filter on)?
Here's how Merlin does it. Note the first check there, making sure that
if (ds->type != NEBTYPE_SERVICECHECK_PROCESSED), it returns immediately.
--8type != NEBTYPE_SERVICECHECK_PROCESSED
|| ds->check_type != SERVICE_CHECK_ACTIVE
|| cb != NEBCALLBACK_SERVICE_CHECK_DATA)
{
return 0;
}
--8<--8<--8<--
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]