Managing audit logs using the CLI

All user activities that impact the system, such as configuration changes, are automatically written to a log.

Prerequisites

To manage audit logs:

Go to CLI configuration mode:

hostname > enable
hostname # configure terminal

Display the active audit log file, a list of all audit log files, an archived audit log file, or selected entries in the active audit log:
```
hostname (config) # show log audit
```
Enable the override of the global minimum severity level of audit log messages saved in log files on the local disk:
```
hostname (config) # logging local override class audit
```
Enable the global minimum severity level of the audit log messages with the specified severity level:
```
hostname (config) # logging local override class audit priority <severityLevel>
```
You can select the following severity levels:
- none—Disables logging.
- emerg—System failure.
- alert—Immediate action required.
- crit—Critical condition.
- err—Error condition.
- warning—Warning of possible problem.
- notice—Significant, but normal event (the default).
- info—Information only.
- debug—Debugging information.
Upload the active audit log file to the specified network location:
```
hostname (config) # logging files audit upload current <path>
```
Save your changes:
```
hostname (config) # write memory
```