Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
Is it possible to load Shape (SHP) files into Qlik using Qlik GeoAnalytics and if so is any conversion required?
Qlik Sense Enterprise on Windows, all versions
Qlik GeoAnalytics / GeoAnalytics+ , all versions
Shape (SHP) files can either be loaded from a local file using Qlik GeoAnalytic+ or through an URL using Qlik GeoAnalytics Connector.
1. Copy the zipped shapefile attached to this article to any location (C:\tmp\CHE_Adm3.zip in this example)
2. Launch Qlik Sense, select Create new app and name the app. Press Create and Open app
3. Go to Data load editor and Create new connection
4. Select Qlik GeoAnalytics Connector
5. In the drop-down make sure to select GeoAnalytics Plus and give the connection a meaningful name
6. Press Test Connection to verify the connection and then Save
7. Press Select data
8. Set the following:
9. Press Next, and in the Select data to load check the tables Dataset_simplified as well as Dataset
10. Press Insert script to insert the script into the Data load editor
11. Press Load data to fetch the data into the data model
12. Once data has been loaded into the data model, create a new GeoAnalytics Map object and a GeoAnalytics Area Layer in a new sheet
13. Click Add dimension on the GeoAlaytics Area Layer and select the field Dataset_Simplified_Geometry
14. Verify the shapefile is shown correctly on the map
Note that there may be occasional issues with SHP file quality and the use of differing Coordinates Reference Systems.
This article explains a workaround to schedule automations between specific hours & days of the week. This workaround can be used until a native solution is delivered.
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
Over the next few weeks, many of us will take some time to recharge before heading into the New Year. Why not take some of that time to invest in yourself and explore some of the learning resources available to Talend Academy subscribers?
Best Practices videos are a quick way to sharpen your Talend skills in between other activities. They take only a minute or two, but they distill expertise from Talend consultants to deliver a meaningful learning experience.
Find them by logging in to Talend Academy, clicking the Search Talend Academy tile, then selecting Best Practices from the menu.
If you're a Talend partner, log in to the Partner Academy, then click Browse Catalog and select Best Practices from the menu.
Get a head start on learning more about Talend 8 by spending time with these resources, now upgraded to reflect the new functionality.
The learning plan was upgraded to a Talend 8.0 environment, and the Logging and monitoring in Talend Management Console module was updated to integrate the new logging interface. Personal access tokens are now used to connect from Talend Studio to Talend Cloud throughout the learning plan.
Loading files larger than 50MB from web storage connectors such Dropbox, Office 365SharePoint, SFTP, Amazon S3 and similar leads to:
Data file size exceeded file streaming buffer size. Adjust the StreamingBufferSizeMB setting.
Qlik Sense Enterprise on Windows
Qlik Cloud
The solution requires us to modify the Qlik Sense Engine settings.ini. See How to modify Qlik Sense Engine settings.ini for details on the procedure.
The value cannot be configured in Qlik Cloud. A workaround is to split the big data files by e.g. months.
QLIK-83207
CP-4120
QLIK-82097
Qlik Data Gateway erroring out with "Invalid metadata response (DirectAccess-2201) " message. The error could be due to a different issues.
The cause of the issue is usually configuration, if the suggestions above didn't fix the issue it will be necessary to report the issue for further analysis.
Qlik Data Gateway: Direct Access Data Gateway failing with Internal Error
After upgrading Tomcat from version 9 to version 10, you may encounter issues when starting the SSL-enabled Talend Administration Center, as it only supports Tomcat version 10.1 or higher, starting from patch TPS-5553.
Error: -SSLUtil - SSL Keystore path or password missing. Please check configuration.
After upgrading to Tomcat 10, ensure that your server.xml file (server.xml file is under <TalendAdministrationCenter_HOME>/apache-tomcat/conf ) is updated to reflect the new and supported SSL attributes.
In Tomcat 10, as several attributes have been deprecated or removed entirely, there are differences that can be found like:
By configuring the SSL connector with the correct and supported attributes, you should be able to resolve the issue of starting the SSL-enabled Talend Administration Center after upgrading to Tomcat 10.
For Example
SSL Connector with supported attributes configuration
<!-- Define an SSL Coyote HTTP/1.1 Connector on port 1234 -->
<Connector
protocol="****"
port="1234"
maxThreads="150"
SSLEnabled="true">
<SSLHostConfig>
<Certificate
certificateKeystoreFile="****/.keystore"
certificateKeystorePassword="****"
type="RSA"
/>
</SSLHostConfig>
</Connector>
======================================
Apache Tomcat version 10 introduced several breaking changes, including the deprecation and removal of certain SSL attributes in the server.xml file. As a result, SSL configurations that were functional in Tomcat 9 may no longer work correctly in Tomcat 10 without some necessary modifications.
configure-tls-ssl-in-talend-administration-center
https://tomcat.apache.org/tomcat-10.0-doc/ssl-howto.html
Port 443 is the outbound port used to connect Qlik DataTransfer to the Qlik Cloud tenant. This port cannot be customized.
Qlik Sense URL(s) tested on SSLlabs (ssllabs.com) return the following weak Cipher suites:
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 1024 bits FS WEAK
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK
The steps documented in this article are an example of how cipher suites can be disabled. All steps are to be performed by a Windows Administrator on Windows level and cannot be supported by Qlik Support.
We recommend to consulting with your security or Windows administrator before proceeding as they may have automated practices in place.
The security in Qlik Sense does not depend only on the Qlik Sense software. It also relies on the security of the environment that Qlik Sense operates in. This means that the security of, for example, the operating system and the cryptographic protocols (such as TLS/SSL) has to be set up and configured to provide the security needed for Qlik Sense. See Protecting the platform.
You can review and configure the cipher suites order using a Group Policy. See Manage Transport Layer Security (TLS) | Microsoft Learn.
Please refer to fig 1:
This policy determines the cipher suites used by the Secure Socket Layer (SSL). If you enable the policy setting, SSL cipher suites are prioritized in the order specified.
If you disable or do not configure this policy setting, the factory default cipher suite order is used.
SSL2, SSL3, TLS 1.0 and TLS 1.1 cipher suites:
TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_MD5 SSL_CK_RC4_128_WITH_MD5 SSL_CK_DES_192_EDE3_CBC_WITH_MD5 TLS_RSA_WITH_NULL_SHA TLS_RSA_WITH_NULL_MD5
TLS 1.2 SHA256 and SHA384 cipher suites:
TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_NULL_SHA256 TLS 1.2 ECC GCM cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521
How to modify this setting:
Configuring preferred cipher suites for Qlik License Service in Qlik Sense Enterprise on Windows
Qlik Sense Enterprise on Windows any version
This video will demonstrate how to install and configure Qlik-CLI for SaaS editions of Qlik Sense.
Content:
get-command qlik
choco install qlik-cli
if ( -not (Test-Path $PROFILE) ) {
echo "" > $PROFILE
}
qlik completion ps > "./qlik_completion.ps1" # Create a file containing the powershell completion.
. ./qlik_completion.ps1 # Source the completion.
Advanced and additional instructions as seen in the video can be found at Qlik-CLI on Qlik.Dev. Begin with Get Started.
Talend Administration Center Application is going to frozen state and unable to open/load the application from the browser until the services are restarted.
From the logs the error message displays as below:
INFO [Catalina-utility-1] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/tac8] has started.
INFO [main] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server instanceorg.apache.catalina.startup.HostConfig.deployDescriptor Deployment of deployment descriptor [/data/talend/tomcat/conf/Catalina/localhost/tac8.xml] has finished in [26,138] ms.
In <TalendAdministrationCenterInstallation>\apache-tomcat-xx.x.xx\conf>tac8.xml(server.xml)file, need to change the parameter reloadable from "true" to "false" as given below.
From
<Context docBase="/data/talend/apps/tac8.war" reloadable="true" />
to
<Context docBase="/data/talend/apps/tac8.war" reloadable="false"/>
This configuration line in Talend Administration Center refers to the Tomcat configuration used by Talend Administration Center to define the deployment settings for the web application.
Please make sure to stop the services before doing any changes.
This performance issue is probably caused by the configuration setting of parameter reloadable in Tomcat server.xml file. When it is set to true, Tomcat will monitor changes in class files and JAR files in the WEB-INF/classes and WEB-INF/lib directories. If there are updates, Tomcat will automatically reload the web application, which can be useful in development but frequent reloading may affect performance and make Talend Administration Center Application is going to frozen state.
Qlik Replicate version 2024.5 has added support for partitioned tables in PostgreSQL database sources. Sub-partitions on these tables are not currently supported.
This limitation could potentially be worked around by using the ODBC CDC source endpoint. ODBC endpoints must be implemented by our Professional Services team. To easily engage with our Professional Services team, contact your Account Manager.
The feature is on Qlik's roadmap for 2025. Review upcoming Release Notes for details.
To track the current feature request's status, see Qlik's Ideation Portal.
Name: Qlik Replicate for PG as a source RDS, CDC replication not supporting for Table sub-partition and cascaded partition.
ID: 448952
Link (requires previous login)
Design limitation.
00318581
A newly installed Qlik Data Gateway for Direct Access stays disconnected.
The log files read:
"System.Net.WebSockets.WebSocketException (0x80004005): Unable to connect to the remote server
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.Security.Authentication.AuthenticationException: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
at System.Net.Security.SslStream.CompleteHandshake(SslAuthenticationOptions sslAuthenticationOptions)"
and
[Service] [DEBUG] Verifying root certificate with the CA bundle "C:\ProgramFiles\Qlik\ConnectorAgent\caBundle\qcg_ca_bundle.pem"
Remove the software and reinstall it without running the command “connectoragent qcs set_config --ca_bundle_path path-to-ca-bundle-file”
The CA Bundle is needed only in very specific scenarios, as specified in Setting the CA bundle (source, Qlik Help):
Who needs to set the CA bundle?
The CA bundle only needs to be set if you are:
Configuring the bundle unnecessarily will result in connection failures.
If a CA Bundle is indeed needed, verify it is configured correctly.
Setting up a CA Bundle when not needed might break connections.
As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).
This allows for analyzer capacity to be shared across all systems using the same license.
QlikView
Qlik Sense Enterprise on Windows
With a Signed License Key (SLK) applied as a unified license across multiple environments
Here is an example;
A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.)
This can be accessed through: System > Licenses > Professional and Analyzer access.
If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up to date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.
This can be accessed in the Qlik Sense Management Console > License Management > License usage summary
The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.
For local consumption data, each server will store its own consumption and user information.
For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.
For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:
RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495 Analyzer Capacity 6 315dcfab-7448-4f4b-8209-ef34742b1abe
Many reloads are failing on different schedulers with General Script Error in statement handling. The issue is intermittent.
The connection to the data source goes through our Qlik ODBC connectors.
The Script Execution log shows a “General Script Error in statement handling” message. Nevertheless, the same execution works if restarted after some time without modifying the script that looks correct.
The engine logs show:
CGenericConnection: ConnectNamedPipe(\\.\pipe\data_92df2738fd3c0b01ac1255f255602e9c16830039.pip) set error code 232
Change the reading strategy within the current connector:
Set reading-strategy value=engine in C:\ProgramFiles\Common Files\Qlik\CustomData\QvOdbcConnectorPackage\QvODBCConnectorPackage.exe.config
reading-strategy value=connector should be removed
Switching the strategy to engine may impact NON SELECT queries. See Connector reply error: Executing non-SELECT queries is disabled. Please contact your system administrator to enable it. for details.
QB-8346
The TAC configuration page's Artifact section displays an error for JFrog access check:
error unauthorized : https://<JFROG_PLATFORM_URL>:<PORT>/access/api/v1/system/ping
$ curl -u "admin:password" "https://<JFROG_PLATFORM_URL>:<PORT>/access/api/v1/system/ping"
{
"errors" : [ {
"code" : "UNAUTHORIZED",
"message" : "Unsupported authentication method Basic"
} ]
}
For every Access-related API, you must use an admin-scoped Access Token or an Admin Identity Token. For further details, please refer to How to generate access token from JFrog admin UI.
Talend Management Console plan is triggered and keeps on "Running" status, but the task shows "Successful" in the status.
Need to manually terminate the plan from the screen to check whether it will solve the issue.
It may be a bug in the user interface (UI) of the Talend Management Console that Plan might be in an inconsistent status.
The Qlik NPrinting Designer (February 2024 IR to SR2) may fail to start. The error thrown is:
HTTP Call Error Sending Request
This is a known defect (QB-30815) and is actively being investigated. A permanent fix is planned for a future patch of the February 2024 release.
This workaround is applied to the Qlik NPrinting Server's webengine.config.
<!-- <add key="include-user-filters" /> -->
<add key="include-user-filters" />
Too many user filters.
QB-30815
It is recommended to enable HTTPS for Qlik GeoAnalytics Server. This can be done either during the installation or by editing the config.ini after the installation.
The deployed SSL certificate may need to be updated regularly, which requires a repeat of the initial installation steps.
The recommended way to enable HTTPS is to run the installation package and set/change the certificate during install. Setting the certificate during install will automatically obfuscate the password stored in config.ini.
[SSL]
sslEnabled=true
sslPort=443
sslKeystore=c:\\path_to_certificate\\certificate_filename.pfx
sslPassword=certificate_password
Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.
Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.
This article provides information on available apps for each platform.
The Data Capacity Reporting App is a Qlik Sense application built for Qlik Cloud, which helps you to monitor the capacity consumption for your license at both a consolidated and a detailed level. It is available for deployment via the administration activity center in a tenant with a capacity subscription.
The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.
The Access Evaluator is a Qlik Sense application built for Qlik Cloud, which helps you to analyze user roles, access, and permissions across a tenant.
The app provides:
For more information, see Qlik Cloud Access Evaluator.
The Answers Analyzer provides a comprehensive Qlik Sense dashboard to analyze Qlik Answers metadata across a Qlik Cloud tenant.
It provides the ability to:
For more information, see Qlik Cloud Answers Analyzer.
The App Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Sense applications in your tenant.
The app provides:
For more information, see Qlik Cloud App Analyzer.
The Automation Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Application Automation runs in your tenant.
Some of the benefits of this application are as follows:
For more information, see Qlik Cloud Automation Analyzer.
The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.
The app provides:
For more information, see The Entitlement Analyzer.
The Reload Analyzer is a Qlik Sense application built for Qlik Cloud, which provides an overview of data refreshes for your Qlik Cloud tenant.
The app provides:
For more information, see Qlik Cloud Reload Analyzer.
The Report Analyzer provides a comprehensive dashboard to analyze metered report metadata across a Qlik Cloud tenant.
The app provides:
For more information, see Qlik Cloud Report Analyzer.
Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:
For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.
The OEM Dashboard is a Qlik Sense application for Qlik Cloud designed for OEM partners to centrally monitor usage data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas.
Although this dashboard is designed for OEMs, it can also be used by partners and customers who manage more than one tenant in Qlik Cloud.
For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.
With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.
If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.