Skip to main content Skip to complementary content
Qlik Resources

Performance log

Qlik Sense Repository Service (QRS)

The following fields are specific to the Performance log for the QRS:

  • Tracenumber: A unique ID for the call to the QRS REST API.
  • Httpmethod: The HTTP method that was used (Get, Put, Post, or Delete).
  • Url: The URL that was used.
  • Resourcetype: The type of resource.
  • Method: The backend code that was called.
  • Elapsedmilliseconds: The time (in milliseconds) to complete the call to the QRS REST API.

Example: Get http://mytest/cars/4

  • Httpmethod: Get
  • Url: http://mytest/cars/4
  • Resourcetype: cars
  • Method: get/cars/{0}

Qlik Sense Proxy Service (QPS)

The following fields are specific to the Performance log for the QPS:

  • ActiveConnections: The number of active connections (in any form or shape) from the client.

    • A connection is a stream (that is, a socket) between a Qlik Sense client and the Qlik Sense Proxy Service (QPS). This stream is often connected to another stream, which runs from the QPS to the Qlik Sense Repository Service (QRS) or the Qlik Sense Engine Service (QES). The two streams allow the client to communicate with the QRS or the QES.

  • ActiveStreams: The number of active data streams (that is, sockets), either from the browser to the QPS or from the QPS to the QRS or the QES.
  • ActiveSessions: The number of active sessions in the QPS.

    • A Qlik Sense user gets a proxy session when the user has been authenticated. The session is terminated after a certain period of inactivity.

  • LoadBalancingDecisions: The number of users who currently have at least one engine session.
  • PrintingLoadBalancingDecisions: The number of users who have been load balanced to the Qlik Sense Printing Service (QPR).
  • Tickets: The number of issued login tickets that have not yet been consumed.
  • ActiveClientWebsockets: The number of active WebSockets between the client and the QPS.
  • ActiveEngineWebsockets: The number of active WebSockets between the QPS and the target Qlik Sense service.
Tip noteThe logging entries are also available as metrics; see Proxy service.

Qlik Sense Engine Service (QES)

Each entry (that is, row) in the Performance log corresponds to a snapshot (that is, a number of measurements) of the performance of the QES at the given point in time.

The following fields are specific to the Performance log for the QES:

  • ActiveUserDirectory: The user directory for the user.
  • ActiveUserId: The ID of the user.
  • EngineTimestamp: The time when the QES wrote the log message to file.
  • EngineThread: The ID of the thread that was used when the QES wrote the log message to file.
  • ProcessId: The ID of the QES process from which the log message originates.
  • Exe Type: The configuration type (release or debug version) of the QES process.
  • Exe Version: The version number of the QES process.
  • Server Started: The time when the QES started.
  • Entry Type: The reason (Server Starting, Normal, or Server Shutting Down) for the log entry in the Performance log.
  • ActiveDocSessions: The number of active engine sessions at the given point in time.
  • DocSessions: The number of engine sessions at the given point in time.
  • ActiveAnonymousDocSessions: The number of active anonymous engine sessions at the given point in time.
  • AnonymousDocSessions: The number of anonymous engine sessions at the given point in time.
  • ActiveTunneledDocSessions: The number of active tunneled engine sessions at the given point in time.
  • TunneledDocSessions: The number of tunneled engine sessions at the given point in time.
  • DocSessionStarts: The number of started engine sessions since the previous snapshot.
  • ActiveDocs: The number of active apps in the QES at the given point in time.
  • RefDocs: The number of apps in the QES at the given point in time.
  • LoadedDocs: The number of loaded apps in the QES at the given point in time.
  • DocLoads: The number of app loads in the QES since the previous snapshot.
  • DocLoadFails: The number of failed app loads in the QES since the previous snapshot.
  • Calls: The number of calls to the QES since the previous snapshot.
  • Selections: The number of selections in the QES since the previous snapshot.
  • ActiveIpAddrs: The number of IP addresses of active connected clients in the QES at the given point in time.
  • IpAddrs: The number of IP addresses of all connected clients in the QES at the given point in time.
  • ActiveUsers: The number of active users in the QES at the given point in time.
  • Users: The total number of users in the QES at the given point in time.
  • CPULoad: A measurement of the load on the CPU on which the QES runs at the given point in time.
  • VMCommitted(MB): The committed Virtual Memory (in megabytes) at the given point in time.
  • VMAllocated(MB): The allocated Virtual Memory (in megabytes) at the given point in time.
  • VMFree(MB): The freed Virtual Memory (in megabytes) at the given point in time.
  • VMLargestFreeBlock(MB): The largest freed Virtual Memory block (in megabytes) at the given point in time.

Learn more

 

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here