||1 - 2147483647 by default, but can be configured using custom logging as described in Qlik Sense Appenders. Each row in the log starts with a sequence number that is used to ensure that the log is not tampered with (that is, that no rows are inserted or deleted). The sequence number wraps either when the last sequence number is reached or when the logging, for some reason, is restarted without the last sequence number being reached.
||Timestamp in ISO 8601 format, YYYYMMDDThhmmss.fffK, where:
For example, 20110805T145657.000+0200 means year 2011, month 8, day 5 at 14:56:57 GMT+2.
- YYYY: Year
- MM: Month
- DD: Day in month
- T: Delimiter
- hh: Hour
- mm: Minutes
- ss: Seconds
- fff: Milliseconds
- K: Time zone offset
||Row log level, can be configured using custom logging as described in Qlik Sense Appenders:
- Debug: Information useful to developers for debugging purposes. This level is not useful during normal operation since it generates vast amounts of logging information.
- Info: Normal operational messages that may be harvested for reporting, measuring throughput, and so on. No action required.
- Warn: Not an error message, but an indication that an error may occur, if no action is taken (for example, the file system is 85% full). Each item must be resolved within a given time.
- Error: Non-urgent failures that are relayed to developers or administrators. Each item must be resolved within a given time.
- Fatal: Indicates a failure in a primary system (for example, loss of primary ISP connection) and must be corrected immediately.
- Off: No logs, except for license logs, are produced.
Note: Starting with the May 2021 release all execution completion log entries are logged as Info instead of Debug.
||Logger in <Facility>.<Service>.<Fully qualified name of class> format, where:
- Application: Log events that are related to the app running in Qlik Sense.
- Audit: Log events that provide an audit trail of a user’s activities and administration of the Qlik Sense platform.
- Exit: Log events that are related to the shutdown of the Qlik Sense Engine Service (QES).
- License: Log events that are related to the Qlik Sense license.
- ManagementConsole: Log events that are related to the Qlik Management Console (QMC).
- Performance: Log events that are related to the performance of the Qlik Sense platform or app.
- QixPerformance: Log events that are related to the performance of the QIX protocol in the QES.
- Security: Log events that are related to security issues.
- Session: Log events that are related to the termination of a proxy session.
- SSE: Log events that are related to server-side extensions.
- Synchronization: Log events that are related to the synchronization of the Qlik Sense Repository Service (QRS) instances in a multi-node site.
- System: Log events that are related to the Qlik Sense platform and not to the app running on the platform (for example, log messages related to the QMC, QRS, Qlik Sense Proxy Service (QPS), and so on).
- TaskExecution: Log events that are related to the execution of tasks by the Qlik Sense Scheduler Service (QSS).
- Traffic: Log events that are related to debugging.
- UserManagement: Log events that are related to the management of the users.
- <Service>: The Qlik Sense service that the log originates from (for example, QRS or QPS).
- <Fully qualified name of class>: Indicates the part of the service that generated the log message.
||Thread name or Managed Thread ID (if available).
||Globally Unique Identifier (GUID) for the log message.
||Name of the user or account used by the Qlik Sense service.
Note: This field is only present when there is an exception message.
A trace to the place in Qlik Sense where the exception occurred.
Note: This field is only present when the Exception field is present.
The ID of the proxy session for the user.
Note: This field is not present in all log files.
|Id2 or Checksum
||The last field in a log entry either contains an Id2 or a Checksum:
- Id2: Log message GUID (same as Id described earlier). This is the normal value.
- Checksum: To protect logs that contain sensitive information (for example, audit, security, and license logs) from tampering, the last field in such log entries contains a cryptographic hash of the entire row up to the hash itself.