The audit log is available through both the controller GUI and the REST API, and records events related to activities, operations, and configuration changes initiated by an authorized user. This includes activities such as:
The values for the AuditLogManager component keys determine the alert age-out policies. The following table describes the keys for the AuditLogManager component (
Specifies the number of days to retain a log entry. Use this key to implement your record retention policy.
Specifies how often, in hours, the controller is to delete log entries that have exceeded the
Updates the log entries displayed on the screen. The controller does not update the display as new entries are generated. Use this action to refresh the display.
The user that performed the operation that triggered the log entry
A time stamp (in UTC format) indicating when the controller created the log entry.
The type of activity that triggered the creation of the log entry.
The application or controller component that generated the log entry.
Detailed information about the log entry.
A hexadecimal number that identifies controller that generated the log entry. When you use controller teaming, this ID enables you to identify which controller in the team generated the alert.
You cannot delete or modify a log entry. The controller deletes entries according to the configured audit log policies. To configure the audit log policies, see “Configuring audit log policies”
Change the values for the keys. For information about the keys and values for this component, see “About audit log policies”.
To retain log records for longer than the
trim.auditlog.age limit, you must export the audit log from the controller to a file before the
trim.auditlog.age limit is reached. Exporting audit log data does not remove it from persistent storage.