Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jan 23, 2023 2:20:11 AM
Apr 13, 2021 4:32:30 AM
This article lists available endpoints for health checks against Qlik Sense Enterprise on Windows services.
These can be used with software automation to check if Qlik Sense work properly but require authentication.
Service name | Endpoints |
Qlik Repository Service | GET /qrs/about can be called to check if Qlik Repository Service is running correctly. Qlik Sense QRS API using Xrfkey header in PowerShell |
Qlik Engine Service | |
Qlik Proxy Service |
|
Qlik Scheduler Service | Primary: GET https://primary-hostname:5050/qss/alive Secondaries: GET https://secondary-hostname:5151/qss/alive PowerShell sample available in Qlik Sense Enterprise on Windows reloads fail with no node found but node is shown as online |
Qlik Printing Service | GET https://hostname/printing/alive can be used to check if the service is alive. It will return 200 if the service is operational, or anything else if not. |
Qlik Logging Service | No healthcheck endpoint available |
Qlik Service Dispatcher |
Qlik Service Dispatcher is not a service by itself but a subset of microservices. Please check below article for main micro-services healthcheck endpoints: Qlik Sense for Windows: Service Dispatcher main services healthcheck endpoints |
For Amazon ALB healthcheck or other simple healthcheck methods without authentication, it is recommended to use the following endpoint to check if Qlik Sense hub/QMC can be reached:
Service name | Endpoints |
Qlik Proxy Service | GET /qps/user When not logged in, this endpoint would return HTTP code 200 and {"session":"inactive"} When logged in, it will return the userDirectory, userId and userName for the currently logged in user. |