The audit log provides detailed information relating to the activities within an OMAG Server.
The audit log is implemented by the Open Metadata Repository Services. It builds on the Audit Log Framework to support multiple destinations for the audit log records written to the audit log by the server's subsystems.
Each audit log record written to the audit log includes information about the component that created it, the server/thread it was running in, a severity code, message description and information on how to fix the problem.
Figure 1: Structure of the audit log record.
The structure is defined by the Audit Log Framework (ALF). The Open Metadata Repository Services (OMRS) extends the record structure with the list of severity codes designed for the open metadata ecosystem.
||The server is providing information about its normal operation.|
||An event was received from another member of the open metadata repository cohort.|
||A decision has been made related to the interaction of the local metadata repository and the rest of the cohort.|
||An Action is required by the administrator. At a minimum, the situation needs to be investigated and if necessary, corrective action taken.|
||An error occurred, possibly caused by an incompatibility between the local metadata repository and one of the remote repositories. The local repository may restrict some of the metadata interchange functions as a result.|
||An unexpected exception occurred. This means that the server needs some administration attention to correct configuration or fix a logic error because it is not operating as a proper peer in the open metadata repository cohort.|
||Unauthorized access to a service or metadata instance has been attempted.|
||A new component is starting up.|
||An existing component is shutting down.|
||An auditable action relating to an asset has been taken.|
||Activity is occurring that relates to the open metadata types in use by this server.|
||The server is exchanging registration information about an open metadata repository cohort that it is connecting to.|
||This is additional information on the operation of the server that may be of assistance in debugging a problem. It is not normally logged to any destination, but can be added when needed.|
||This log record contains performance monitoring timing information for specific types of processing. It is not normally logged to any destination, but can be added when needed.|
||This log record describes the activity of users. It is not normally logged to any destination, but can be added when needed.|
Raise an issue or comment below