property. For instance: regex=(.*foo.*) Only the line matching the regex will be sent to the dispatcher. For instance, instead of the log collector, you can create the following etc/org test, the line will be parsed as follows (the file collector will send the following data to the dispatcher): first->this second->is third->a fourth->test If the keys configuration is not set, then key-0 here, the line will be parsed as follows (the file collector will send the following data to the dispatcher): key-0->test It’s also possible to use keys to identify each regex group. To use this parser

filter /* <dispatcher>FORWARDdispatcher> <dispatcher>INCLUDEdispatcher> <dispatcher>REQUESTdispatcher> com Event Handler is the processor which processes remote events received through the topic. • Event Dispatcher is the unit which decides which event should be processed by which event handlers. • Command node has a listener registered on that topic and gets/sends all events to the event dispatcher. When the Event Dispatcher receives an event, it looks up an internal registry (in our case the OSGi Service

Event Handler The processor which processes remote events received through the topic. • Event Dispatcher The unit which decides which event should be processed by which event handlers. • Command A special node has a listener registered on that topic and gets/sends all events to the event dispatcher. When the Event Dispatcher receives an event, it looks up an internal registry (in our case the OSGi Service

SLA alerters consume from these topics. Decanter uses EventAdmin topics as monitoring events dispatcher. Collectors, appenders, and alerters are simple OSGi services exposed by different bundles. It implementing SynchronousBundleListener interface: You can see here the usage of the OSGi EventAdmin as dispatcher: the collector creates a data map, and send it to a decanter/collect/bundle topic. We just need