Qlik Collected Data

This page lists what Sifflet imports from Qlik and how it builds lineage.

Imported Assets

Sifflet imports the following assets from the Qlik spaces selected in the source:

Apps and datasets appear in the Data Catalog and in the lineage. Sifflet doesn't import other Qlik objects (sheets, charts, automations). If you need support for other objects, contact Sifflet support.

Collected Metadata

• Apps: name, prefixed with the name of their space ([Space name] App name), and description.
• Datasets: name.
• Table references: table name, and the platform of the Qlik data connection they come from.

Sifflet doesn't collect usage statistics (views) for Qlik assets.

Lineage

Sifflet builds lineage from the Qlik lineage API, which returns the upstream resources of each app: datasets, QVD files, and database tables, and the links between them. Sifflet links database tables to the matching tables of your other Sifflet sources by parsing the connection string of the Qlik data connection.

Lineage to warehouse tables is supported for Qlik data connections to:

• Snowflake
• Google BigQuery

Data Freshness

Sifflet refreshes Qlik metadata on the source's schedule. See Integrations Management for default frequencies and scheduling.

Qlik rate-limits its lineage API, and Sifflet reads the lineage of every app through it: on tenants with many apps, a refresh can take a long time.

Limitations

• Tables loaded through data connections other than Snowflake and Google BigQuery appear in the lineage without links to your warehouse tables.

Sifflet Insights Browser Extension

The Sifflet Insights browser extension supports the following Qlik asset types:

• Apps

Data Exposure

Sifflet only reads Qlik metadata: it never reads or stores the data of your apps or datasets. See Security for more details on the data Sifflet stores.