Configure Audit Settings - Revision history

Vmurrell at 16:18, 30 October 2025

2025-10-30T16:18:12Z

Plazarou: /* Overview */

2024-01-29T13:32:17Z

‎Overview

Vmurrell at 15:42, 4 September 2023

2023-09-04T15:42:09Z

Vmurrell: /* Log Events */

2020-11-10T14:50:42Z

‎Log Events

Vmurrell at 14:19, 10 November 2020

2020-11-10T14:19:19Z

Vmurrell at 14:18, 10 November 2020

2020-11-10T14:18:21Z

Vmurrell: Created page with "CategoryHow_To =Overview= The Fusion Metadata Registry can be used to audit activity, including structure queries, submissions, data registrations, data queries, etc. For..."

2020-11-10T14:13:06Z

Created page with "CategoryHow_To =Overview= The Fusion Metadata Registry can be used to audit activity, including structure queries, submissions, data registrations, data queries, etc. For..."

New page

[[CategoryHow_To]]
=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. 

[[File:Audit7.PNG|1200px]]

=Audit Events=
Auditing can either be enabled or disabled.

'''Audit Level''' 

You can either log '''All Events''' (as shown in the example below) or '''Transactional Events''' only. 

'''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 applied.

[[File:Audit5.PNG|700px]]

=Log Events=

Logging can be enabled or disabled. 

'''Logging Level''' 

You can either log '''Transactional Events''' (as shown in the example below) or '''All Events''' only. 

'''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. 

[[File:Audit6.PNG|700px]]

'''Note''': In order to take advantage of the Rollback feature, Audit must be enabled. [https://fmrwiki.sdmxcloud.org/Restore_(Rollback)_Structures Click here to read more about Structure Rollback.]

@@ Line 1: / Line 1: @@
-[[Category:How_To]]
+[[Category:Fusion Registry Configuration]]
 =Overview=
 '''Important Note: This feature is not available in Version 11.'''

@@ Line 2: / Line 2: @@
 [[Category:Fusion Registry Install]]
 =Overview=
-'''This feature is not available in Version 11.'''
+'''Important Note: This feature is not available in Version 11.'''
 The Fusion 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.

← Older revision		Revision as of 14:50, 10 November 2020
Line 52:		Line 52:
	'''Note''': In order to take full advantage of the Rollback feature, '''Audit Events''' should be enabled. Additionally, if you wish to review the log file prior to performing a Rollback it is wise to switch on '''Log Events'''.		'''Note''': In order to take full advantage of the Rollback feature, '''Audit Events''' should be enabled. Additionally, if you wish to review the log file prior to performing a Rollback it is wise to switch on '''Log Events'''.

−	[https://~~fmrwiki~~.sdmxcloud.org/Restore_(Rollback)_Structures Click here to read more about Structure Rollback.]	+	[https://wiki.sdmxcloud.org/Restore_(Rollback)_Structures Click here to read more about Structure Rollback.]

← Older revision		Revision as of 14:18, 10 November 2020
Line 50:		Line 50:


−	'''Note''': In order to take advantage of the Rollback feature, Audit ~~must~~ be enabled. [https://fmrwiki.sdmxcloud.org/Restore_(Rollback)_Structures Click here to read more about Structure Rollback.]	+	'''Note''': In order to take full advantage of the Rollback feature, '''Audit Events''' should be enabled. Additionally, if you wish to review the log file prior to performing a Rollback it is wise to switch on '''Log Events'''.
		+
		+	[https://fmrwiki.sdmxcloud.org/Restore_(Rollback)_Structures Click here to read more about Structure Rollback.]