From c7916d6b820bde690145450ba02209e741154866 Mon Sep 17 00:00:00 2001 From: Dmitri Pal Date: Fri, 14 Aug 2009 15:05:12 -0400 Subject: ELAPI: Adding concept of targets The targets are the destinations which caller wants to send the events to. The sinks are now on the second level under targets and constitute a so called fail over chain for a target. Such approach eliminates the need for complex routing function. The dispatcher keeps the list of targets in a collection. The element in the collection is the target context. Also gispatcher keeps the list of the sinks in a separate collection. Each target context has a list of the sinks associated with this target. But those are just pointers (at least for now) to the sinks form the list kept by dispatcher. I had to add some internal debug callbacks to be able to see that all the internals of the dispatcher are actually in order. See the conttent of config file for more comments. Also see information posted on SSSD wiki. https://fedorahosted.org/sssd/wiki/WikiPage/ELAPIInterface --- common/elapi/elapi_event.h | 1 + 1 file changed, 1 insertion(+) (limited to 'common/elapi/elapi_event.h') diff --git a/common/elapi/elapi_event.h b/common/elapi/elapi_event.h index f18333962..27c297b18 100644 --- a/common/elapi/elapi_event.h +++ b/common/elapi/elapi_event.h @@ -68,6 +68,7 @@ #define E_BASE_HOSTEXT ( E_HAVE_HOSTALIAS | E_HAVE_HOSTIPS ) #define E_BASE_DEFV1 ( E_BASE_TIME | E_BASE_HOST | E_BASE_APP | E_HAVE_SEVERITY ) + /* The default time stamp format */ #define E_TIMESTAMP_FORMAT "%F" -- cgit