Event Broker
The Event Broker is responsible for:
Converting historic audit and Job run data into the new event format.
Periodically checking for new product usage data.
Writing events to the Event Log file.
Calculating and storing data metrics.
Receiving events from other Privitar services.
Operation
The first time that the Event Broker is started a service runs and queries the Privitar configuration database (ConfigDB) for all events that have taken place on the Privitar platform since the platform was operational. These historical Events are extracted from the Event and JobRun tables stored in the database. (This service will not be run again.)
The Event Broker also receives events directly from Privitar services. These events are passed through by the Event Broker where they are processed to create metric data and written directly to the Event Log.
Configuration
The Event Broker is configured using a properties file (in a similar manner to the application.properties file that is used to configure other features of the Privitar Platform).
The Event Broker configuration options include:
The type of database to be queried. Options include: PostgreSQL, Oracle and MySQL.
The username and password credentials for the Configuration Database. These credentials can be encrypted in the same way that these details are encrypted in the main application.properties file.
Startup options for the Event Broker.
Event Log
Event data is stored in the Event Log in JSON format. Files will be split when they reach a certain configurable size. These are the files that will be sent back to Privitar or that you can analyze at your site for your own data analytics.
Metric Store
Specific events are processed by the Event Broker to create running metrics that can be displayed in the Policy Manager. The Metric Store captures the number of PPOs and the number of records processed over time.
These figures are stored in a separate schema/database to the configuration database. Values are aggregated and written every minute to reduce the number of rows being created in the database.
The Metric Store supports the same database types as the configuration database.