6. Event Handling¶
DATAGERRY uses an event based communication between its daemons. Each daemon can publish and subscribe events to a message broker. The message broker (currently, RabbitMQ is supported) will route events to the different daemons.
Each daemon will open two AMQP connections to the message broker (one for sending, one for receiving events). The connection handling will be done by cmdb.event_management.event_manager.EventManagerAmqp.
6.1. structure of an event¶
An event consists of a type and a set of key-value pairs as parameters.
id: id of the new created object
The set of key-value pairs depends on the event type.
6.2. event routing¶
Events are routed by type to the daemons. Each daemon can subscribe to a list of event type definitions. In these definitions, wildcards can be used:
# subscribe to a specific event type cmdb.core.object.added # subscribe to all event types starting with a specific string cmdb.core.#
6.3. list of event types¶
The following event types are defined in DATAGERRY:
These events will be created by the core system if CMDB objects will be added/updated/deleted. The parameter “public_id” which includes the public ID of the specific object will be included.
These events will be created by the core system if CMDB object types will be added/updated/deleted. The parameter “public_id” which includes the public ID of the specific object will be included.