About the system log

You can use the system log to track usage and detect potential security problems. The system log can help you detect erroneous or malicious behavior as it occurs. You should check the system log first if the Marketing Platform application malfunctions or if you think a break-in might have occurred or been attempted.

The system log contains the following information.

Configuration information and all errors and debugging information for the Marketing Platform.

A record of key events as they occur on the Marketing Platform server (requests, grants, revokes, and failures).

About the configuration settings displayed in the system log

The first part of the system log shows the configuration settings that are read into the system from the uasm.conf configuration file on startup. Viewing the configuration settings in the log file is an easy way to check settings that control properties for IBM® EMM passwords, the Marketing Platform authentication data store, the Marketing Platform web server root, and the system log and system audit trail.

If a problem occurs when the system attempts to write to the system log file, the system writes to stdout (command line) instead of to a file.

System log entry format

The system log entries are in the following format.

Timestamp | Event severity level | Message

Timestamp - The time the event occurred.

Event Severity Level - The logging level of the event.

Message - Description of the event. If the entry is a request to the server, the message typically contains the function called by the request. Response entries record the results of the requests.