Junos Space Audit Logs Overview
Audit logs provide a record of Junos Space login history and user-initiated tasks that are performed from the user interface. From the Audit Logs workspace, you can monitor user login/logout activity over time, track device management tasks, view services that were provisioned on devices, and so forth. Junos Space audit logging does not record non-user initiated activities, such as device driven activities, and is not designed for debugging purposes. User-initiated changes made from the Junos Space CLI are logged but are not recorded as audit logs.
To use the audit log service to monitor user requests and track changes initiated by users, you must have Audit Log Administrator.
![]() | Note: Audit Logging is not currently supported for Campus Builder and Service Now. |
Over time, the Audit Log administrator will archive a large
volume of Junos Space log entries. Such log entries might or might
not be reviewed, but they must be retained for a period of time. The
Archive Purge feature helps you manage your Junos Space llog volume,
allowing you to archive log files and then purge those log files from
the Junos Space database. For each Archive Purge operation, the archived
log files are saved in a single file, in CSV format. The audit logs
can be saved to a local server (the server that functions as the active
node in the Junos Space fabric) or a remote network host or media.
When you archive data to a local server, the archived log files are
saved to the default directory /var/lib/mysql/archive.


