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.

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 in the connector catalog.

The audit log destination connectors supplied with Egeria are described in the Connector Catalog

Egeria Audit Log Destination Connectors¶

Below are the connector implementations provided by Egeria

• Console Audit Log Connector writes selected parts of each audit log record to stdout.

• slf4j Audit Log Connector writes full log records to the slf4j ecosystem.

• File Audit Log Connector creates log records as JSON files in a shared directory.

• Event Topic Audit Log Connector sends each log record as an event on the supplied event topic.

• Console Event Display Audit log Destination displays the content of events in the console when they are both received and sent.

• PostgreSQL Audit Log Destination stores audit logs in a PostgreSQL database.

Raise an issue or comment below