Qlik

Sifflet connects to Qlik Cloud to show which apps depend on the tables you monitor in your data warehouse. When an incident affects an upstream table, you see right away which Qlik apps are impacted, and from an app you can trace the datasets, QVD files, and warehouse tables that feed it. For the full list of imported assets and metadata, see Qlik Collected Data.

🚧

Beta

The Qlik integration is in beta. Contact Sifflet support to share feedback or report an issue.

Permissions Required

Sifflet reads Qlik Cloud metadata through the Qlik Cloud REST APIs, with a machine-to-machine (M2M) OAuth client that authenticates with the client credentials flow. Sifflet only reads metadata: it doesn't modify apps and doesn't read app data.

At each refresh, Sifflet reads the lineage of every app through the Qlik lineage API. Qlik rate-limits this API to a few requests per minute per tenant (Qlik's "Special" rate-limit tier), so the first run on a tenant with many apps can take a long time.

Requirements

Required Roles for Setup

• In Qlik Cloud: the Tenant Admin role, to create an OAuth client and add it to spaces.
• In Sifflet: a role that can create credentials in Integrations > Credentials and sources in Integrations > Sources.

Supported Versions and Editions

Sifflet supports Qlik Cloud tenants only. Qlik Sense Enterprise on Windows (client-managed, self-hosted) isn't supported: if you use it, contact Sifflet support.

Network Access

Qlik Cloud is a SaaS service: Sifflet connects to it over the internet.

• IP allowlisting: if you restrict access to your Qlik Cloud tenant with IP allowlists, allow the IP addresses of your Sifflet instance, listed in Settings > Integration Preferences.

Other Prerequisites

To see lineage from your warehouse tables to Qlik apps, add the warehouses that Qlik reads from as sources in Sifflet first. See Lineage for the supported warehouses.

Connect Sifflet to Qlik

Step 1: Create an OAuth Client in Qlik

1. In the Qlik Cloud administration console, create a machine-to-machine (M2M) OAuth client. See the Qlik documentation on creating an OAuth client.
2. Grant the client the following scopes:
   • admin.spaces:read
   • admin.apps:read
   • user_default
3. Copy the client ID and client secret. Qlik shows the client secret only once: store it securely.
4. For every Qlik space that contains data connections, add the OAuth client as a member with the Can consume data permission.

Keep the client ID and client secret for step 2.

Step 2: Add the Qlik Source in Sifflet

1. Go to Integrations > Credentials and create a credential with the client ID and client secret of the OAuth client, in the following format:

   JSON

   {
     "user": "<OAUTH_CLIENT_ID>",
     "password": "<OAUTH_CLIENT_SECRET>"
   }

2. Go to Integrations > Sources, click New source, and select Qlik.

3. Fill in the source fields:

   Field	Description	Example
   Name	The name of the source in Sifflet	Qlik production
   Host	The URL of your Qlik Cloud tenant, with https:// and without any path	https://<TENANT>.<REGION>.qlikcloud.com
   Credentials	The credential created above	qlik-oauth-client

4. Click Load assets to list the Qlik spaces that the OAuth client can access, then select the spaces to import. Sifflet only imports the apps and datasets of the selected spaces: leave out spaces that don't contain production apps.

5. Click Test Connection. Sifflet checks that it can list spaces, apps, and data connections, and read the lineage of one app. Then save the source.

Saving the source starts a first run. You can follow its status and logs in the source details, and the assets appear in the Data Catalog when the run completes. To change the selected spaces later, edit the source: apps and datasets of spaces you deselect disappear from Sifflet at the next run. For refresh frequency, scheduling, and other source operations, see Integrations Management.

Troubleshooting

For errors returned by Test Connection (no spaces, apps, or connections found, no access to the lineage API), see Qlik Troubleshooting.