NEW! Content Monitor for Qlik Sense Enterprise on Windows

[SavRakkar]

The new Content Monitor loads from the APIs and logs to present key metrics on the content, configuration, and usage of your platform, allowing administrators to understand the evolution and origin of specific behaviors of the platform.

• Basic information can be found in Content Monitor | help.qlik.com  
• Each sheet in the Content Monitor includes an About text box to describe its content. 
  

This new monitoring app comes pre-installed with the latest version (November 2025 onwards) of Qlik Sense Enterprise on Windows.

If you are running previous versions of Qlik Sense Enterprise on Windows, the Content Monitor is also available on Qlik's Downloads page here: Content Monitor (download page) - note, this must be manually installed and a weekly reload is recommended.

[Lynn_W]

Thank you @VictorGonzalezFaria ,

Just in case I cleaned up our AboutService folder on every node, it had almost 900 logs going back to 2018 in there. 😄  The latest was just from Saturday.  I was still getting the error so I pulled the load script up to the top to look at just this piece.  It works just fine when I run it in my workspace, it shows the correct version.  When I run it from the QMC it is not getting anything to populate the ProductInfo table.  Is there a user ID that needs to be added to the security rule for the ServerLogFolder Data connection?  Our Service Account already has access.

[VictorGonzalezFaria]

Hello @Lynn_W,

The default ServerLogFolder Data connection points to C:\ProgramData\Qlik\Sense\Log as the default configuration is single-node. When converting into a multi-node, the connection must be changed to always read that folder from the Central as described in this Help article, something like "\\myCentral\SharedLogs".

If that is not done, it will be reading from the C:\ProgramData\Qlik\Sense\Log folder of the Scheduler executing the reload, where the AboutService folder will exist, but will not contain the required information.

That applies in general for Folder Data connections in multi-node environments, they should not point to "drive letter" (C:, D:, etc.), but to network location (\\myCentral, \\mySharedDrive, etc.).

Hope this helps,

VG

[Lynn_W]

Hello @VictorGonzalezFaria ,

Thank you, that was the breadcrumb I needed.  We have our environment split into Central, Consumer, and Scheduler Nodes.  The logs in the AboutService folder on the Central and Scheduler Nodes is only 4 lines long.  The Logs on the Consumer nodes are 16k lines long.  I pointed the connection to one of the Consumer nodes and the app got past this section of the code.  App ran for 1.5 hours then died with "General Script Error in statement handling".  I'm trying again.

[Or]

@VictorGonzalezFaria After clearing out all of the older logs from the AboutService folder, I'm still getting Call ThrowException('The Content Monitor App requires Qlik Sense Client-Managed February 2020 or greater (>=13.62.x). This site must be upgraded to use this application.')

I checked the oldest remaining log file and it's definitely a newer version than Februrary 2020.

What am I missing? In general I'm a bit lost as to why we can't just teach the Content Monitor to ignore logs that are from older versions and move to the next one... 

[VictorGonzalezFaria]

@Or,Hello 

If this is a multi-node environment, I would expect it to be related to the configuration of the ServerLogFolder Data connection.

I'm copying from a previous response:

**************************

The default ServerLogFolder Data connection points to C:\ProgramData\Qlik\Sense\Log as the default configuration is single-node. When converting into a multi-node, the connection must be changed to always read that folder from the Central as described in this Help article, something like "\\myCentral\SharedLogs".

If that is not done, it will be reading from the C:\ProgramData\Qlik\Sense\Log folder of the Scheduler executing the reload, where the AboutService folder will exist, but will not contain the required information.

That applies in general for Folder Data connections in multi-node environments, they should not point to "drive letter" (C:, D:, etc.), but to network location (\\myCentral, \\mySharedDrive, etc.).

**************************

Please comment if the platform is multi-node and if the suggstions works.

VG

[bsk717]

Hello,

Any one got fixed this Issue. App reload is failed as there is no Version details in Log even though i am using Nov-2025 Patch3.

[Lynn_W]

@bsk717  I have this working now. I'm on a multi-node environment that has been set up since early 2018.

first go out to ArchivedLogsFolder and delete or rename the folder content-monitor-qvds to _old if you have been able to get that far and it has created some QVDs.

On the configuration tab

vCentralNodeHostName: I was able to leave Set vCentralNodeHostName = 'localhost';

Set vFolderScanIsDynamic = 0;

IndividualFolderConnectionsToScan: add the data connections for the locations you store files and logs.

vServerLogFolder: This one you need to go to your nodes and check the AboutService sub-folder.  The log in my central is only 4 rows.  The log on rim2 (primary proxy) has the data the app is looking for.  Set vServerLogFolder = 'lib://RIM2/'; (or where your full log lives).

I did have to fix a couple of my monitoring apps to write their QVDs to the same location for this one to work.

Set vGovernanceLogContentFolder = 'lib://ServerLogFolder/';

Under the optional configuration 

Set vFileScanReferenceDay = 0;  This defaults to a range of dates.  The first time you run the app it checks the date range and skips this part if the current date is outside the range.  When you run it for the second time, the QVD doesn't exist that would have been created and the load fails.

I hope this helps get you started.

[bsk717]

Thanks @Lynn_W  for your prompt reply. I haven’t tried the suggested fix yet. However, in my case I identified the issue.

 

The Productinfo:Raw table wasn’t loading files from the AboutService Log folder because there was an extra backslash in the server log folder path. After removing the extra backslash from the connection string, the script loaded correctly without requiring any other changes.

[Sander_Persgroep]

The script of this app works perfectly when I run it from the Load Editor. However, it doesn't work from the QMC. From the QMC, we get the error: "Error: The remote server returned an error: (404) Not Found.".

Help page:
"https://help.qlik.com/en-US/sense-admin/November2025/Subsystems/DeployAdministerQSE/Content/Sense_De..."

Provides:

---

Failed to connect to the QRS via the Qlik REST Connector.

Information note: This problem will only occur if you have apps that work with the Qlik REST Connector.

An error message is displayed indicating a problem connecting to the QRS via the Qlik REST Connector.

Possible cause

The Qlik REST Connector is unavailable, because it has been uninstalled or corrupted.

Proposed action

If the error message appears during a reload, you need to verify that the Qlik Sense installation is working properly. Consider repairing or upgrading Qlik Sense.

---

The Content monitor uses "monitor_apps_REST_app".

This connection returns data in the Data Load Editor....

Yesterday, we upgraded our environment to Nov25 Patch 3. Is this an installation error?

[VictorGonzalezFaria]

Hi @Sander_Persgroep, the QMC run is triggered in a node where the Virtual Proxy is not associated and hence, localhost/Windows fails.

• The App should be load balanced to run from the Central (if no changes on load balancing rules, publishing to the Monitoring Apps stream should suffice), or
• A node associated to the Virtual Proxy should be named in the vCentralNodeHostName variable in the ** configuration ** section, instead of "localhost", so the call is sent to that node. Using the central there is often a good measure, as long as the Virtual Proxy is associated to it.

You can check the node where the QMC run is triggered by looking at the "i" icon in the task, or in the log, look for:

Let startMsg      = 'Reloading Content Monitor 1.0.1 from **** running QIX Engine version ***'

Hope this helps,

VG