Skip to content

Audit Log Destination Connector

An audit log destination connector provides support for a specific audit log destination. At least one audit log destination connector is configured in every OMAG Server's configuration document and used by its audit log component when the server runs.

Audit Log Destination Connector

An audit log destination's purpose may be either to store, process or distribute audit log records to diagnostic systems. Its associated configuration controls which severities of audit log record it receives. The implementation for the audit log destination connector can make further choices about how each log record is processed.

An OMAG Server can have multiple audit log destinations configured. This configuration can control which severities of audit log record are sent to each destination.

The implementation for the audit log destination connector can make further choices about how each log record is processed.

The interface for audit log destination connectors is located in the repository-services-apis module. The audit log destination connectors implemented by Egeria are described below.

Egeria Audit Log Destination Connectors

Below are the connector implementations provided by Egeria

Observing activity

To analyse the activity recorded in the audit log - for example, to see which metadata elements are most used - use the Pepys Activity Observer and the Lovelace services, which turn audit log records published on an event topic into open metadata.

Further information relating to Audit Log Destination Connectors

Raise an issue or comment below