The Sense Connector Logs Analyzer app lets you investigate patterns of activity and errors to troubleshoot connector performance.
The app relies on log files generated by REST connector version 1.7 or later and ODBC connector version 5.12 or later.
Log files from older versions of REST and ODBC connectors may not include the necessary column header names which will cause the Sense Connector Logs Analyzer app to fail during reload. It is recommended that these older connector log files are removed or moved to a separate folder.
Importing the Sense Connector Logs Analyzer app to the Monitoring apps in the QMC
The Sense Connector Logs Analyzer is not available by default from the QMC. To make it available, you need to import the app.
Follow the instructions in the section Importing new Monitoring apps
No configuration is needed for single-node deployments but it is possible to modify the days of log history to load in the load script. You can also include Engine, Repository, Scheduler and Proxy logs in the app.
Days of history
The days of history is set as a variable, vu_days_of_history, in the load script.
Default is 14 and it is not recommended to exceed 90 days of history due to potential volume of data.
You can include Sense Engine, Repository, Scheduler and Proxy logs in the app setting the vu_load_operations_monitor_qvd variable.
This gets the Operations Monitor historical QVD from the ServerLogFolder data connection.
Multi-node deployment configuration
Multi-node environments require the creation of new data connections to a shared folder, like \\FQDN\CustomData, of each node. The data connections are then defined in the vu_data_connection_list variable in the load script.
Share the C:\ProgramData\Qlik folder on each node.
Name the shared folder Custom Data.
Add a new data connection for each rim node. Use the Fully-Qualified Domain Name (FQDN) of each node.
Create a data connection called connector_logs_rim2 to point to folder \\rim_node_2\Custom Data\.
In the QMC > Data Connections section, rename the new data connections created in the previous step to remove the user name which is appended to the data connection name.
connector_logs_rim2 (my_domain\my_user1) should be renamed to connector_logs_rim2.
In the QMC > Data connections section, update the Connection string of the monitor_apps_connector_logs data connection, located on the Identification tab, so it uses the FQDN of the central node.
\\central_node_name\Custom DataNote: If user permissions were set on the shared folder, you need to define the User ID and Password fields accordingly. Else leave undefined.
Update the load script to add the data connections created and renamed in the previous steps.
The data connections are defined in the vu_data_connection_list variable. Each data connection is enclosed within the existing single quotes and separated with a comma.
Example:SET vu_data_connection_list = 'monitor_apps_connector_logs,connector_logs_rim2,connector_logs_rim3';
Save the updated app.
Reload the app.
You can reload the app from the QMC or from the data load editor.
Sense Connector Logs Analyzer sheets
The Sense Connector Logs Analyzer sheets display usage and errors for Qlik connectors across all nodes.
Visit the story About the Sense Connector Logs Analyzer for details about the sheets, available from the app overview page, under Stories.