Sense Connector Logs Analyzer

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.

Note: For a more detailed description of the sheets and visualizations, visit the story About the Sense Connector Logs Analyzer that is available from the app overview page, under Stories.

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

General configuration

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.

Note: The configuration is done in the Configuration section of the load script.

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.

Example:  

SET vu_days_of_history = 14;

Historical 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.

Tip: You must enter the name of the QVD to load without the .qvd extension.

Example:  

SET vu_load_operations_monitor_qvd = 'governanceLogContent_7.10.2_db';

Multi-node deployment configuration

Multi-node environments require the creation of new data connections to \\FQDN\C$\ProgramData\Qlik\Custom Data\ of each node. The data connections are then defined in the vu_data_connection_list variable in the load script.

Note: The configuration is done in the Configuration section of the load script.
  1. Add a new data connection for each rim node. Use the Fully-Qualified Domain Name (FQDN) of each node.

    Example:  

    Create a data connection called connector_logs_rim2 to point to folder \\rim_node_2\C$\ProgramData\Qlik\Custom Data\.

  2. 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.

    Example:  

    connector_logs_rim2 (my_domain\my_user1) should be renamed to connector_logs_rim2.

  3. 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';
  4. Save the updated app.

  5. 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.

Note: Data in the Sense Connector Logs Analyzer is updated when the app is reloaded. Data is not live.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?