Skip to main content

Operations Monitor

ON THIS PAGE

Operations Monitor

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.

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

For the location and naming convention of the log files, see Logging.

With the Operations Monitor, you can track system performance and investigate activity that might adversely affect it. For example, by analyzing reload tasks and sessions, you can find bottlenecks that might be alleviated by rescheduling reloads or redistributing sessions. Or you can use the QMC Change Log sheet to review changes that might explain changes in system performance.

Operations Monitor sheets

The Operations Monitor sheets display Qlik Sense performance on the current node, and, when properly configured for multi-node (as described in Configuring multi-node environments), the app includes information across all nodes.

Operations Monitor sheets
24-Hour Summary Displays hardware utilization, active users, active apps, and reload tasks over the last twenty-four hours.
Performance Allows the user to select a time period over which to display hardware utilization, concurrent users, and concurrent apps.
Task Overview Provides a statistical overview of the success, duration, and failure of reload tasks.
Task Planning Provides details about reload count, reload CPU spent, and task dependencies.
Task Details Provides details about the success and failure of individual app reloads, including execution details about duration and start and end times.
Session Overview Provides summary information about apps, app sessions, and app users over selected periods to show which users use which apps when.
Session Details Provides details about individual user and app sessions, including number, average duration, days since last session, start and end times, reasons for ending sessions, and the type of client on which the app was run.
Export Overview Provides summary information about apps, app objects, and app users to show which users export which app objects when.
Sheet Usage

Provides summary and detailed information about users accessing sheets – and which sheets in which apps are not accessed.

The Unused sheets measures count the number of sheets within an app which have not been used within the selected time frame. For example, 10 "Unused base sheets last <=30 days" means that 10 sheets have not been used in the last 30 days.

Apps Provides details about the apps in the Qlik Sense Repository Service (QRS), including name and ID of app objects, owners, publishing, and streams.
QMC Change Log Displays changes made in the QMC that affect a range of factors from system performance to user access, including changes by QMC resource type, by specific QMC resources, by users who made changes, or by a type of action performed in the QMC.
Export Links for Cloud Provides details about app links to export to SaaS editions of Qlik Sense, which can then be imported in SaaS editions of Qlik Sense as generic links. To be able to add the links to the cloud hub or upload them to the management console, you must first export the links into a CSV file. See Exporting links into .csv files.
Log Details Provides details about reloads of the Operations Monitor, including the time of reloads, results, error messages and warnings, and log entries.
Note: Data in the Operations Monitor is updated when the app is reloaded. Data is not live.
Note: Operations Monitor uses the ProxySessionId from the engine's session logs for deriving its session counts like Sessions Monitor. This effectively gives the proxy session counts, which can be slightly lower than License Monitor and Sessions Monitor session counts due to the way those apps calculates their sessions. Operations Monitor excludes short sessions (less than 40 seconds) that get registered in Sessions Monitor due to their respective design choices.