Event Architecture

An event architecture will be created in eBox to report events over any kind of dispatcher to inform about different issues that usually happen in eBox.

The Architecture

Event Watcher

It will be the subject (Observer pattern) which intends to call all the registered watcher to get known if any event has ocurred. An ebox-watcher will be executed as a daemon that it will check every steptime for executing any concrete watcher. Once an event has been raised, it is sent to the Event Dispatcher which dispatches the event to the dispatchers that the event watcher decides. If any dispatcher is not plugged, the event is not sent over this dispatcher. This issue is silently ignored.

Concrete Watcher

It will be one the watcher. An example could be a DiskFullWatcher which takes care if the disk is full to fill it out more. It will be called by ebox-watcher whenever its periodicity says so. Every watcher can decide to where the event will be dispatched, any is an option to send everywhere possible.

Event Dispatcher

It receives events from the event watcher. Its burden is sending the event to where the event says so depending on the possibilities.

Event Concrete Dispatcher

It is in charge of dispatching the Events to anywhere. An example could be to the control center, to the Web interface, mail to the admin or whatever.