Home > Multi-tenant administration > Multi-tenant monitoring
Multi-tenant monitoring
Last updated: 2026-11-03Cadence: Daily (rollups) and Monthly (data-source refresh)
Subscription model: Multi-tenant subscriptions
Roles: Tenant Admin (TA), Analytics Admin (AA)
Last verified: 2026-05
| Initial | Recurring | |
|---|---|---|
| Estimated time | 1 day | 5 min daily / 30 min monthly |
Benefits:
- Single pane of glass over the multi-tenant estate
- Simplified secret management by aggregating to one tenant
- Aggregated capacity / entitlement view alongside per-tenant detail
Goal
Per the Monitor your deployment guidance on qlik.dev, the recommended pattern is to deploy the monitoring apps to a single, central tenant so that secret management for the third-party store used for aggregation stays simple. The community-supported monitoring apps from the qlik-cloud-monitoring-apps repo—App Analyzer, Entitlement Analyzer, Reload Analyzer in particular—have been tested on deployments of thousands of tenants.
Tools
| Tool | What it does | Notes |
|---|---|---|
| OEM Dashboard | Single pane of glass over the multi-tenant estate; pulls from App Analyzer, Entitlement Analyzer, and Reload Analyzer | Designed for OEMs but explicitly supported for any customer / partner managing >1 tenant. Community-supported. |
| Console Settings Collector | Optional companion to the OEM Dashboard; harvests configuration data from each tenant | Distributed alongside the OEM Dashboard releases; community-supported. |
| Multi-tenant toggle in App / Entitlement / Reload Analyzers | Lets the same monitoring apps aggregate data from multiple tenants into the central tenant | Same apps are usable per-tenant or in multi-tenant aggregation mode. (Monitoring Applications support multitenancy) |
| Data Capacity Reporting App | Auto-consolidates capacity data across tenants in a capacity-based subscription | Fully supported by Qlik. Tenant identifiers only—no name / metadata enrichment at present. |
Tasks
| Task | TA | AA | DA | AuA | SAO |
|---|---|---|---|---|---|
| Designate a central monitoring tenant and deploy OEM Dashboard + Console Settings Collector there | ✓ | ||||
| Configure each managed tenant to feed data into the central tenant (per the OEM Dashboard install guide) | ✓ | ✓ | |||
| Track new-tenant additions and decommissionings in the OEM Dashboard data sources so the multi-tenant view stays current | ✓ | ✓ | |||
| When using the Data Capacity Reporting App, maintain your own external mapping of tenant ID → tenant friendly name (the app doesn't enrich) | ✓ |
Automation helpers
- Capacity consumption app deployer (Qlik Automate template)—Deploys the Data Capacity Reporting App listed above.
- Qlik Cloud Monitoring Apps Deployer—Deploys the App / Entitlement / Reload Analyzers in their multi-tenant aggregation mode.
- Qlik Cloud Monitoring Apps API Key Rotator—Rotates keys across each managed tenant feeding the central tenant.
References
- Monitor your deployment (qlik.dev)
- Multitenant Deployment with Qlik (Qlik blog)
- qlik-cloud-monitoring-apps repo (multi-tenant compatibility matrix)
- qlik-cloud-oem-dashboard repo
- Monitoring Applications support multitenancy (announcement)
Tags: #daily #monthly #multi_tenant #monitoring #oem_dashboard #central_tenant