...
UES provides the means by which event messages, generated by Universal Agent components whenever they perform actions that impact the computing environment on which they execute, are recorded, routed, and managed.
...
Event messages are collected by Universal Brokers from components that run local to the Brokers. UEC, in turn, collects the event messages from the Brokers and stores them as event records in the UES database (uec.evm.db) for long-term management and access.
...
In order to generate and capture event messages, each Agent component that is able to generate event messages has an EVENT_GENERATION option. This option controls which event message types to generate.
By default, EVENT_GENERATION is set so that no event message types are generated. The value must be set so that event messages of interest are generated by the component.
...
Event message expiration is controlled with the Universal Broker MONITOR_EVENT_EXPIRATION and PERSISTENT_EVENT_EXPIRATION options. These options specify the number of seconds that an event message should remain in the UES database before it is eligible for deletion. Each event message contains the time that it was recorded in the database. The Broker considers an event message expired if the difference between the current time and the recorded time is greater than the option value.
...
A Broker provides UES database access to UEC. UEC sends a request to a Broker asking for the latest event messages. The Broker responds with event messages that satisfy the UEC request.
The Universal Broker EVENT_ACCESS Universal Access Control List (UACL) entry control read and delete access to the UES database.
The default EVENT_ACCESS rule allows read access and denies delete access. These UACL defaults allow any UEC read access to event messages while denying all UECs delete access to event messages.
...