CentraSite 10.5 | CentraSite User’s Guide | Runtime Governance | Runtime Events and Key Performance Indicator (KPI) Metrics | CentraSite Configuration to Receive Run-Time Events and Metrics | Event Modeling
 
Event Modeling
An event is an instance of an event type. Events are modeled in a separate schema from the event type schema. CentraSite models events as non-registry objects (to avoid storing large amounts of unwanted event data in the registry or repository) and instead stores event data in a database collection within the Event Receiver. CentraSite maps events to their corresponding event types using the event types' UUIDs. Similarly, events are mapped to target types, targets and services using UUIDs, and the event type attributes.
The stored event data contains:
*The event Trap ID (MIB OID).
*The event Trap value that consists of:
*The attribute key (MIB OID).
*The attribute value.
The event data is stored in the Event Receiver as an events doctype.
If an event contains payloads (for example, File-Type attributes such as ResponsePayload and RequestPayload), the payloads are stored in the Event Receiver as a payloads doctype, and is referenced by the event stored under the event doctype, using ino:id. This is used to reduce de-serialization of the usually large payloads and to improve performance of queries on the stored events.