Audit Log preferences
To open the Audit Log Preferences dialog box, select . Use this dialog box to customize the operation of the Audit Log and Audit Log Viewer dialog box.
This table shows the audit log preferences options:
Option | Description |
---|---|
Specifies the maximum number of entries that are shown in the Audit Log Viewer dialog box. | |
Determines whether events are automatically listed in the Audit Log Viewer dialog box when they are
reported in the Audit Log. New
events are added to the list in the position that is appropriate for the
currently selected sort. If the list contains the maximum number of entries (see above), then the final (or first) entry is deleted when a new one is added. Deletion order is specified by the user. If this option is selected, then the command is not available. |
|
Specifies if the message content should be recorded into the audit log.
By default, it is cleared. If it is selected, then the Audit Server records the message content into the audit log file when viewing or resending SMAT messages or outputting the extra-long form of message data through the Database Administrator. If the message content is recorded, then it is encrypted before being written to the log file. The transmission to the client side, viewed on the Audit Log Viewer, is encrypted to ensure safety. When resending, the Audit Server records the message content of the modified messages. For unmodified messages, the Audit Server records only their message IDs. When a message is changed and resent, you can view the message content under any of these conditions:
In the Audit Log Viewer, you can view the content when is enabled. The entry for the resent message is prefaced with "GRANTED execute permission." |
|
Specifies whether a log entry should be split into multiple entries
before being written to the audit log file. This option is enabled when
When this option is selected, the kilo-characters box is enabled. This is used to set the maximum size of the message content to be logged onto one log entry. By default, the maximum size is 1000 kilo-characters. A log entry whose message content exceeds the specified maximum size is automatically split into multiple ones. The generated log entries have the same log message and are written to the log file in sequence to ensure they are in a group. Each log entry logs part of the message content. The content size for the log entry is determined by the specified maximum size. This indicates that each log entry takes the maximum size to log the message content until the whole message content is logged. When the message content is from a SMAT message, a different way of splitting the message content is used to avoid breaking the integrity of the SMAT message. Each log entry always logs the entire SMAT message. When the size of the SMAT messages in one log entry exceeds the maximum size, the last messages is moved to the next log entry to record until the current size is appropriate. When the size of a SMAT message exceeds the maximum, there is no splitting in one log entry. |
is selected, because whether the log entry is
split is up to the logged message content size.