Monitoring current performance and availability of Qlik Sense site is not out-of-the-box feature, but can be easily achieved with native REST connector and requesting engine\healthcheck JSON API.
There are other tools and approaches, but since I already have the best BI tool available 😉, I found it reasonable to use it. All that is necessary is just:
download and import the attached app
create REST Data Connections and adjust the settings in the script
schedule app reload
This Qlik Sense app:
loads engine\healthcheck JSON data from multiple nodes
parses and consolidates it to two tables
stores them to QVDs with all previous snapshots
visualizes key metrics of engine utilization and availability in time
It's recommended to deploy and schedule this app on DEV or TEST site, pointing to all production nodes. Otherwise, there will be no data loaded in case the production engine (or the whole server) crashes. (just FYI - DEV and TEST sites are included in the professional license subscription)
It's also recommended to read the official help site info about the engine API before you deploy this app.
After importing the app to a suitable site, follow these steps:
1. Decide on target folder for result QVD files, where parsed snapshot of JSON data will be stored. Create a folder Data Connection (if it doesn’t already exist) and set its Lib name to vQVDpath variable in Settings script section.
2. Create a REST Data Connection to each node:
URL: https://<server domain>/engine/healthcheck OR https://<node IP address>:4747/engine/healthcheck
Authentication Schema: Windows NTLM User name & password: type root admin or service user credentials check "Skip server certificate validation" if there is no valid certificate on target node
Query headers: User-Agent: Windows Cache-Control: no-cache
3. Adjust the INLINE table in the Settingssection of the script according to your site
node - name of the node that will be shown for app’s user restConnection - name of the REST connection that points to node’s engine/healthcheck RAM - amount of node's memory in GB CPU - number of node's logical processors
4. Schedule a reload task. The recommended app reload frequency is 5 minutes or less (tested reload duration on the 4-node site is 12 seconds). The script will return "N/A" in [isSaturated] field when the engine is not responding.
The current roadmap includes - script for email notifications, possibility to load only N days back, mapping app name to IDs, node comparisons.
PLEASE! If you make adjustments or additions to the script or front-end visualizations, please share them back on the Qlik Community.