Tracking user activities

The Audit Log can be used to track user activities that happened during runtime. It records the accessing of message data and dumping of message content into the audit log file. With the increase in log information being written into the audit log file, you must to cycle the log file.

The Audit Log can track and cycle in these ways:

  • Logging who outputs the extra-long form of message data through the Database Administrator and when it was performed. Optionally, you can log the output message content.

    See Audit Log preferences.

  • Logging who views and resends SMAT messages and when it was performed. Optionally, you can log the SMAT message data including the message metadata and message content. For resending, only the modified message data is logged.

    See Audit Log preferences, Audit Log Viewer dialog box, and Audit Log detail panel.

  • Logging who reads the engine log, including which log file name, time and data.
  • Sorting log entries by date.

    See Sorting log entries.

  • Providing automatic cycling ability for the Audit Log.
  • Providing a cycle command line for manually cycling the Audit Log.
  • Splitting a log entry into multiple entries when the entry size exceeds the maximum limitation.

    See Audit Log preferences.

  • Encrypting the logged message content of the audit log file to prevent attempts to view sensitive message data.

    See Audit Log preferences.