How do you leverage QlikView logging and auditing tools for debugging and testing your QlikView development?

1 QlikView Logging Levels

QlikView has four logging levels that determine the amount and type of information that is recorded in the log files, ranging from no logging to errors, warnings, and additional information. You can set the logging level for each QlikView document in the Document Properties dialog box, under the General tab, or for the QlikView Server and the QlikView Publisher in the QlikView Management Console, under the System tab. This allows you to customize how much information is recorded in your log files.

2 QlikView Log Files

QlikView generates several log files that store information about the QlikView documents, the QlikView Server, the QlikView Publisher, and the QlikView Web Server. These log files are located in different folders, depending on your installation and configuration. You can use the QlikView Log Viewer tool to view and filter the log files, or open them with a text editor or a spreadsheet application. Some of the most common log files include the Document Log, which stores data about reloads and distributions such as start and end times, script execution, data sources, variables, triggers, and errors/warnings. The Server Log contains info on the QlikView Server service like start/stop time, license validation, memory usage, document loading/unloading, user sessions, and errors/warnings; it is stored in C:\ProgramData\QlikTech\QlikViewServer by default. Additionally, the Publisher Log stores information about tasks execution and distribution status; it is stored in C:\ProgramData\QlikTech\Publisher\Qlikview Distribution Service by default. Lastly, the Web Server Log holds data on HTTP requests/responses, authentication methods, and errors/warnings; it is stored in C:\ProgramData\QlikTech\WebServer by default. Reporting and documenting these logs will help inform stakeholders and provide valuable insights for improving cloud security posture.

3 QlikView Debugging Mode

QlikView offers a debugging mode that allows you to identify and fix errors or issues in your data load or transformation logic. This mode can be accessed from the Script Editor by clicking on the Debug button. Once in the debugging mode, you can run your script line by line with the Step button, or until a breakpoint with the Run button. Additionally, you can set and remove breakpoints by clicking on the line numbers in the script. Furthermore, you can limit the number of records or tables that are loaded from your data sources with the Test Load option, to speed up the debugging process. Lastly, the Table Viewer and Data buttons let you view the structure and content of your data tables, fields, and associations, while the Variables and System Fields buttons let you view values and expressions of your variables and system fields.

4 QlikView Performance Tuning

QlikView has several tools and techniques that can help you optimize the performance of your QlikView applications. The QlikView Performance Monitor, which is available in the QlikView Management Console, allows you to monitor and analyze the performance metrics of your QlikView Server and documents. The QlikView Optimizer, which is accessible from the Script Editor, helps you compare and test different data load and transformation scenarios. Additionally, there are several best practices for improving your QlikView applications, such as using incremental load for new or updated data, binary load for data from another document, optimized load for loading data from QVD files, pre-calculated expressions for complex calculations, set analysis for filtering data based on predefined criteria, synthetic keys to avoid circular references or ambiguous associations, and document chaining to link multiple documents.

5 QlikView Auditing Tools

QlikView has several tools that can help you audit and secure your QlikView applications, such as the QlikView Governance Dashboard and QlikView Security Settings. The Governance Dashboard lets you analyze and report on the metadata and usage of your environment, such as data sources, data models, expressions, reloads, distributions, licenses, and users. Security Settings provide options to protect documents and data from unauthorized access or modification; these include Document Password, Section Access, Hidden Script, and Document Log. Document Password lets you set a password for opening a document in addition to user authentication; Section Access allows for control of data visibility based on user roles and permissions; Hidden Script hides part of the script from other users or developers; and Document Log enables or disables logging to track or prevent recording reload and distribution information.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?