Difference between revisions of "Fusion Edge Server Audit"

From Fusion Registry Wiki
Jump to navigation Jump to search
(Audit File)
(Audit File)
Line 8: Line 8:
 
   EdgeServerAudit_<launch time>_<log index>.json
 
   EdgeServerAudit_<launch time>_<log index>.json
 
For example:  
 
For example:  
   EdgeServerAudit_1699022799196_1.json  
+
   EdgeServerAudit_1704067199000_1.json
  
Where the launch time value is the time, in milliseconds since 1970, of when the Edge Server was started.
+
The "launch time" value represents the time when the Edhe Server was started. However, this value is expressed as a lengthy numerical figure, indicating the time in milliseconds since 1970.
  
Audit information will be written to this file untile either the Edge Server is terminated or the file reaches the file limit of 10Mb in size. If the file limit is reached a new file is created with the next incremental Log Index value.
+
Audit information will be written to this file until either the Edge Server is terminated or the file reaches the file limit of 10Mb in size. If the file limit is reached, a new file is created with the next incremental Log Index value. Log files that are actively being written to may be "locked" by your Operating System until either the Edge Server is terminated or a new log file is started.
  
This file does not contain formatted JSON. The best way to view it is to use a formatter tool, such as JSON Line.
+
Each Audit file contains JSON, but this is not formatted for ease of reaability. Until the file is "completed", either by termination of the Edge Server, or by a new log file being started, a final closing brace character "]" is required to make the file contents become valid JSON. So you may find that if you wish to look at the currently being written Audit file you have to:
 
+
- Create a copy of the Audit file
This file may be locked by your Operating System. If you wish to view it (and format it) you may have to make a copy first
+
- Open this copy in the editor of your choice (for example Notepad++)
 +
- Add a final "]" character to the end of the file
 +
- Format the JSON for readability/
  
 
== Disabling Audit ==
 
== Disabling Audit ==

Revision as of 09:59, 16 January 2024

This page explains details the Audit capabilities of Fusion Edge Server.

Audit File

All Audit information from Fusion Edge Server is written to Audit files which are located in the "Audit" sub-folder of your [[Fusion_Edge_Server_Directory|Edge Server Directory]. Audit files are named according to the format:

 EdgeServerAudit_<launch time>_<log index>.json

For example:

 EdgeServerAudit_1704067199000_1.json

The "launch time" value represents the time when the Edhe Server was started. However, this value is expressed as a lengthy numerical figure, indicating the time in milliseconds since 1970.

Audit information will be written to this file until either the Edge Server is terminated or the file reaches the file limit of 10Mb in size. If the file limit is reached, a new file is created with the next incremental Log Index value. Log files that are actively being written to may be "locked" by your Operating System until either the Edge Server is terminated or a new log file is started.

Each Audit file contains JSON, but this is not formatted for ease of reaability. Until the file is "completed", either by termination of the Edge Server, or by a new log file being started, a final closing brace character "]" is required to make the file contents become valid JSON. So you may find that if you wish to look at the currently being written Audit file you have to: - Create a copy of the Audit file - Open this copy in the editor of your choice (for example Notepad++) - Add a final "]" character to the end of the file - Format the JSON for readability/

Disabling Audit

Auditing can be disabled by modifying the Edge Server properties file and adding the entry:

 audit.disabled=true

See the [[Fusion_Edge_Server_Properties|properties page] for more information.