The Logs Inventory displays system wide events for the purpose of operation confirmation, health monitoring, fault diagnosis and auditing.
Figure. Logs Inventory
| Control | Description |
|---|---|
 Purge Logs |
Removes all logs of a given age and older from the log manager database. Logs marked as 'Audit' cannot be removed. The Purge Logs Dialog is displayed prior to the logs being purged. |
 Edit purge schedule |
Allows the automatic log purge schedule to be configured. The Log Purge Schedule is displayed. |
 Acknowledge All Error Logs |
Acknowledges all unacknowledged error logs in the log database. Unacknowledged error logs are displayed with a red background. Acknowledged logs are displayed in green and the acknowledgment message, date and time are displayed alongside the log entry. The Acknowledge Logs Dialog is displayed prior to the logs being acknowledged. |
 Export Logs |
Exports the log database as a file, respecting the currently specified filter terms. The Export Logs Dialog is displayed prior to the logs being exported. |
 Acknowledge Selected Logs |
Enabled only if one or more log entries are selected. Acknowledges all selected logs in the log database. Unacknowledged error logs are displayed with a red background. Acknowledged logs are displayed in green and the acknowledgment message, date and time are displayed alongside the log entry. The Acknowledge Logs Dialog is displayed prior to the logs being acknowledged. |
 Create Log Notification |
Enabled only if one log entry is selected. Creates a log notification condition for that log message type. The Notification Wizard is displayed to assist in creating the notification condition. |
 Condensed View |
Display a subset of the log fields in the log table. |
 Extended View |
Display all of the log fields in the log table. |
| Log Entry | Refer to the Log Fields table below for a full description of all fields. |
| Filter on Message | Filters the log table so that only logs containing the specified string in the Log Message field are displayed. |
| Filter on Date Time Range | Filters the log table so that only logs from the specified Master date and time are displayed. Opens the Date Time Range Picker. |
| Filter on Actioned By | Filters the log table so that only logs relating to the specified node that performs an action are displayed. |
| Filter on Actioned For | Filters the log table so that only logs relating to the specified node that requests an action are displayed. |
| Filter on Category | Filters the log table so that only logs of the specified Category are displayed. |
| Filter on Log Level | Filters the log table so that only logs of the specified Level and above are displayed. |
| Filter on Acknowledgement | Filters the log table so that only acknowledged or unacknowledged logs are displayed. |
| Filter on Log Type | Filters the log table so that only audit logs are displayed. |
| Field Name | Description |
|---|---|
 Select Log Entry |
Each log entry can be selected using the selection checkbox. Click one or more log entries to apply an action to that item. |
 Sequence Number |
All logs have a sequence number associated with them representing the order in which they arrived at the master node. Some logs that are used for statistics and reporting do not appear in the log inventory and consequently there will gaps in the displayed sequence numbers. |
 Audit |
Audit logs are marked with a  icon. Click on the Audit icon if present to display the audit information for the corresponding log message. Audit messages cannot be removed from the log database. |
 Session |
Logs relating to a session are marked with a  icon. Click on the Session icon if present to display all log messages that pertain to that same session. The Session Log Details is displayed. |
| Master Date | The date and time at which the log message was stored within the master node’s log database. Each log entry appears in the log table in descending time order, with the latest log displayed first. |
| Local Date | The date and time at which the message was actually logged by the machine that generated the message. Due to network speed, connectivity issues or different time zones this can differ from the Master Date. |
| Actioned By | The machine from which the specific action is performed. |
| Action For | The machine that requested the specific action. |
| Category | The Protector component that generated the log. A special category named Session is used to indicate the start and end of a sequence of log entries relating to a specific transaction or job. Refer to Session Log Details for details. |
| Level | How important the log message is. This can be one of four values:
|
 Attachment |
A  icon is displayed if an attachment is included with the log entry. It provides further information that can aid understanding. Click on the Attachment icon if present to display the Log Attachments Dialog which shows additional supporting information that cannot be displayed within the log table. |
| Log ID | A unique identifier that enables that log message to be looked up in the knowledge base. Not all log entries have a Log ID assigned (i.e. the ID is set to 0). If you require assistance regarding an unassigned ID, please contact support. |
| Log Message | The actual text content of the log message. When searching this field, words that are entered in the search box must appear in the log message text. Log messages are displayed with alternating background shading to aid readability. |
| Acknowledgment | A note entered by the user who acknowledged the log message and the date & time of acknowledgement. (See Acknowledgement Selected Logs button). |
Detail – These log messages can describe intricacies of a process, or non-critical information and do not require any action by the user.
Information – These messages give a higher-level overview of a process, and usually indicate normal operation. These messages do not require any action by the user.
Warning – Messages logged at warning level can indicate that the user should investigate the subject of the message to see if it requires further action. Warning messages are not necessarily critical.
Error – Error messages are only logged when the attention of the user is required. They appear with a red background and cause an error badge to appear on relevant nodes within the