Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Audit log

Qlik Sense Repository Service (QRS)

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

  • Action: The action that the user performed (add, update, delete, export).
  • ActiveUserDirectory: The user directory for the user.
  • ActiveUserId: The ID of the user.
  • ResourceId: The ID of the resource on which the user performed the action.

Qlik Sense Proxy Service (QPS)

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

  • ConnectionId: The ID of the connection.
  • ActiveConnections field in Performance log

  • ActiveUserDirectory: The user directory for the user.
  • ActiveUserId: The ID of the user.
  • TicketId: The ID of the login ticket that was issued for the user. The ticket ID exists until it is consumed by the QPS.
  • IpAddress: The IP address of the client.
  • AppId: The ID of the app (empty if no app is loaded).
  • TargetHost: The call from the client is forwarded to a Qlik Sense Engine Service (QES) or QRS. This field contains the name of the machine on which the service is running.
  • VirtualProxy: The virtual proxy prefix in {prefix} format.

Qlik Sense Engine Service (QES)

The following fields are specific to the Audit 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.
  • ServerStatus: The time when the QES started.
  • AppId: The ID of the app.
  • Type: The type of operation that the user performed to generate the audit message.
  • Qlik Sense User: The user who generated the audit message.

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!