Difference between revisions of "Audit Settings"
(→Overview) |
(→Audit Events) |
||
| Line 19: | Line 19: | ||
=Audit Events= | =Audit Events= | ||
| − | The Fusion Metadata Registry enables auditing to be enabled or disabled. If auditing is disabled, no audit events will be captured. | + | The Fusion Metadata Registry enables auditing to be enabled or disabled. If auditing is disabled, no audit events will be captured. |
'''Delete Audits Every''' input filed can be set how many days the audit events should be kept for, if the field is left empty then the audits will never be deleted. It is important to note that this setting is only relevant for non-transactional events. Transactional audit events will not be deleted even if this setting is set.<br> | '''Delete Audits Every''' input filed can be set how many days the audit events should be kept for, if the field is left empty then the audits will never be deleted. It is important to note that this setting is only relevant for non-transactional events. Transactional audit events will not be deleted even if this setting is set.<br> | ||
Revision as of 09:36, 5 November 2020
Overview
The Fusion Metadata Registry can be used to audit activity, including structure queries, submissions, data registrations, data queries, etc. For each audited event, the associated server side logs can be captured and stored against the event. The Audit tab in the settings Registry Settings enables the level of auditing to be controlled, and the definition of which log events are captured can also be set. Audit and log information can be given a lifetime after which time they will be deleted.
Audit events are split into two categories:
1. Transactional
These audit events are ones which result in the Registry modifying structures, data, or metadata. A transactional event includes structure submissions, data registrations, and reference metadata submissions.
2. Non Transactional
These audit events are one where information is being read from the Registry, but no information is being modified. These events include (amongst others) data queries, structure queries, and schema queries.
Audit events are used to capture additional information for structure modifications.
They are also used to provide an overview of User Activity as shown in the image below.
Audit Events
The Fusion Metadata Registry enables auditing to be enabled or disabled. If auditing is disabled, no audit events will be captured.
Delete Audits Every input filed can be set how many days the audit events should be kept for, if the field is left empty then the audits will never be deleted. It is important to note that this setting is only relevant for non-transactional events. Transactional audit events will not be deleted even if this setting is set.
Audit Level
You can either log All Events (as shown in the example below) or Transactional Events only.
Log Events
Logging can be enabled or disabled. If logging is enabled, the Logging Level can be used to define that logs should only be captured for transactional events.
Delete Logs Every can be used to specify the number of days or hours that the server logs should be kept for, leaving this filed blank will be used to indicate the logs should never be deleted. Note log events will only be deleted for non-transactional audit events.
Audit Level
You can either log Transactional Events (as shown in the example below) or All Events only.
Note: In order to take advantage of the Rollback feature, Audit must be switched on. Click here to read more about this feature.
