Built by Solve: Task Monitor Application for Qlik Cloud (QSEoCS)

We have been working with one of our Qlik Sense Enterprise on Cloud Services (QSEoCS) clients. They were one of the first companies to move from Qlik Cloud Business to QSEoCS.

We’ve discovered that there is a key feature missing in QSEoCS: a Task Monitor to easily see, in one place, the status of all scheduled jobs.

To help fill this void in the current offering, we built a quick-and-dirty Task Monitor application that leverages the REST API Connector and the QSEoCS API.  The application reloads and loops through REST API calls for a set number of loops. In our client’s environment, that provides about 10 days of history.  A future enhancement would be to build in incremental load logic. We want to share this dashboard app with you. Here are detailed steps on how to build and configure it:

Allowing API Connectivity

Administration Configuration:

From the QSEoCS Hub > Go to Administration Area:

Under the Configuration > Settings, scroll down to the API Keys area and…

  1. Enable API Keys
  2. Modify the maximum token expiration so that you don’t have to regenerate the keys all the time.

Under Users, adjust user role to allow API Keys:

Under Hub > Settings, go to the User Settings area:

Under Settings > API Keys

…click Generate new key, and name an API Key.

Rest API Connector

In the normal Qlik Load Script area, create a REST API Connection:

  • Connection: https://<InstanceName>.us.qlikcloud.com/api/v1/reloads
  • Method: GET
  • Query Header:
    • Authorization: Bearer+<Space> + API Key
    • Limit Loads: 100 (I set to 100 so it pulls 100 rows each time it runs)

Qlik Sense Load Script

In general, the script is fairly straight-forward. (I’m more of a technical sales resource, so I’m sure it could be cleaned up a bit.)

Steps:

  • Reload Primer
    • Do initial calls to build initial tables
  • Reload Loop
    • Repeat calls on a loop appending data to tables
  • Get Application Names
    • Call to API to get Application Names (Reload just gave App IDs)
  • Final Prep
    • Transform/Cleanup
  • Calendar
    • Leveraged AutoCalendar (Simplified to Year, Month, YearMonth, Week and Date)
    • Applied AutoCalendar to Start Time and End Time Date/Time fields

Here is a link to the Task Monitoring Application so you can use it: Link to GitHub.

If you have any questions, or would like help getting this up and running in your environment, we are happy to help. Please feel free to email us at info@Solve100.com

Greg Woodard

Principal at Solve