Service log

The version number of the Qlik Sense service (for example, 1.2.1.3).

Timestamp in ISO 8601 format, YYYYMMDDThhmmss.fffK, where:

• YYYY: Year
• MM: Month
• DD: Day in month
• T: Delimiter
• hh: Hour
• mm: Minutes
• ss: Seconds
• fff: Milliseconds
• K: Time zone offset

For example, 20110805T145657.000+02:00 means year 2011, month 8, day 5 at 14:56:57 GMT+2.

Row log level, can be configured using custom logging as described in Appenders:

• Debug: Information useful to developers for debugging purposes. This level is not useful during normal operation as it generates vast amounts of logging information.
• Info: Normal operational messages that may be harvested for reporting, measuring throughput, and so on. No action is required.
• Warn: Not an error message, but an indication that an error will occur, if no action is taken (for example, the file system is 85% full).
• Error: Messages regarding unexpected situations and errors that prevent the server from operating normally.
• Fatal: Messages that the Qlik Sense service or application has to shut down in order to prevent data loss.

A human-readable message that summarizes the action in the system.

Format:

Command=<CommandName>;Result=<ReturnCode (Int)>;ResultText=<Description, Success, or Error message>

The ID of the proxy session.

0 = Internal system command or a command that does not go through the QPS

A unique ID of each http(s) package that passes through the Qlik Sense Proxy Service (QPS).

0 = Internal system command or a command that does not go through the QPS

The combination of RequestSequenceId and ProxyPackageId is unique for every row in a log file and creates the timeline for the proxy session. The combination also forms a primary key in the log file.

The initial RequestSequenceId is an integer. Subrequests are linked to the initial request by adding a dot and an ID for the subrequest:

• Initial request: RequestSequenceId = 1
  • Subrequest 1 based on the initial request: RequestSequenceId = 1.0
  • Subrequest 2 based on the initial request: RequestSequenceId = 1.1

0 = Internal system command or a command that does not go through the Qlik Sense Engine Service (QES)

The user directory linked to the logged in Qlik Sense user.

System = Internal system command

The Qlik Sense user that initiated the command.

System = Internal system command

The internal ID of the object. Used to link system actions to user actions.

0 = Cannot get the ID of the object

In some cases the ObjectId field contains multiple IDs, separated by the "|" (pipe) sign.

Example: ObjectId field containing multiple IDs

Log event: Start reload task

Contents of the ObjectId field: ed5715cd-2d7f-44ec-825f-44084efb3443|d63c7e4e-6089-4314-b60f-ed47ba6c35cc

• First ID: The ID of the task.
• Second ID: The ID of the app.

The human-readable name of the object. The ObjectName is linked to the ObjectId.

Not available = Cannot link the ObjectName to the ObjectId or the ObjectId is missing

In some cases the ObjectName field contains multiple names.

Example: ObjectName field containing multiple names

Log event: Start reload task

Contents of the ObjectName field: MyReload|MyApp

• First identifier (MyReload): The name of the task.
• Second identifier (MyApp): The name of the app.

The list of ObjectNames always matches the list of ObjectIds, meaning that the ObjectName in the first position is identified by the ID in the corresponding position of the ObjectId field. In this example the following IDs apply (see also the description of the ObjectId field):

• MyReload = ed5715cd-2d7f-44ec-825f-44084efb3443
• MyApp = d63c7e4e-6089-4314-b60f-ed47ba6c35cc

The origin of the request:

• AppAccess
• ManagementAccess
• Not available

The context of the command.

The context can be Internal System command or User Activity command (based on URL for the command).

Return code:

• 0, 200 - 226: Success
• Any other number: Error