Content Monitor
The Content Monitor app collects data from several logs and APIs to show key metrics about platform content, configuration, and usage. It presents data at multiple levels of detail—from monthly or weekly summaries down to individual records. This helps administrators analyze platform behavior and performance.
The app contains four main types of sheets:
-
Weekly Summary and Snapshot show high-level metrics to monitor platform status and recent trends. Review these sheets weekly.
-
Content-oriented sheets (such as Streams, Applications, Task Hierarchy, and File Inventory) provide lists of content created in or associated with the platform. Use them to review content characteristics or to support clean-up, rationalization, and optimization.
-
Operational sheets (such as Sessions, Task Executions, Data Connections Usage, and their concurrency details) provide insights into platform activity and performance. They serve as a starting point for analyzing workload and identifying areas of stress on the platform. Some sheets also include graphical views or focus on concurrency. Use them to identify trends and deviations in performance or usage, and take action to maintain or improve availability.
-
Infrastructure displays high-level configuration data. Use this sheet to confirm or compare items that may affect platform performance. The information is useful for investigations and quick reviews. The Errors & Warnings and Archived Log Folder Storage sheets help you manage back-end maintenance.
Content Monitor sheets
Most sheets let you filter data to focus on specific items or timeframes. Operational metrics—such as session counts or task executions—are initially calculated and presented for the full investigation period set in the configuration (180 days by default). You can adjust the filters as needed.
| Introduction | Provides a short introduction to the app, showing the version, last reload date and duration, and the configuration parameters used during the reload. |
|---|---|
| Weekly Summary | Presents a collection of instantaneous KPIs, including absolute metrics (for example, number of apps, nodes, or data files), cumulative metrics (such as number of sessions or task executions), and aggregated metrics (such as maximum concurrent sessions or daily average task executions). |
| Snapshot | Shows a collection of instantaneous KPIs, including absolute metrics (for example, number of apps, nodes, or data files), cumulative metrics (such as number of sessions or task executions), and aggregated metrics (such as maximum concurrent sessions or monthly average data load script execution time). |
| Streams | Lists streams with content and usage metrics. The [My Work (Unpublished)] stream represents the work stream of all Professional users, and the metrics represent the accumulation of all of them. Supports high-level filtering and comparison between streams. |
| Applications | Displays all apps with details such as stream, sessions, RAM footprint, and last reload date. Supports filtering, sorting, and identification of apps with specific characteristics. |
| Sessions | Shows overall platform usage and correlations between sessions, apps, and users, specifically app usage patterns in relation to RAM footprint. |
| Session Concurrency | Displays minute-by-minute concurrent sessions and RAM footprint of apps used in the session, including data on the apps with the highest concurrency. |
| Task Executions | Aggregates task execution data including statuses, time distribution, and load balancing. Includes a detailed list with filtering, sorting, and identification of performance outliers. |
| Task Execution Concurrency | Displays minute-by-minute concurrent task executions and peak reload RAM. Peak reload RAM is assumed for the full execution; actual RAM may be lower. |
| Task Hierarchy | Lists all tasks with task chains, showing complete chains and task counts by trigger type. |
| Data Connections Usage | Displays all data connections and their relationships with apps. For folder connections, shows the files found under each connection. |
| File Inventory | Shows counts and sizes of files in folder data connections, helping identify duplicates, storage needs, and unnecessary files. |
| Files Analysis | Extends file inventory data with graphical views for quick identification of trends and outliers. |
| Infrastructure | Summarizes configuration information from the QMC, including service cluster, nodes, engines and scheduler sections. |
| Errors & Warnings |
Shows counts and trends of errors and warnings, broken down by node, service, and error or warning type. Not available if the governance log content QVD from the Operations Monitor cannot be accessed. |
| Archived Log Folder Storage | Displays size, file types, and age of archived logs to help assess logging configuration and potential cleanup needs. |
Configuration
The Content Monitor app is designed to run with its default configuration. You only need to customize settings if your environment requires it.
Customizing the app
There are two configuration sections in the data load script: configuration and optional configuration. Common reasons to customize include:
-
Changing data connection names for archived logs or server log folders.
-
Specifying the central node name for multi-node sites if monitoring apps are not reloaded on the central node.
All configuration options are documented directly in the script.
Adjusting reload scope
You can reduce reload time by limiting the data the app loads. To do this, adjust parameters such as:
-
Number of days for logs lookback
-
Number of days since the last app reload
-
Include or exclude monitoring apps
-
Include or exclude apps by name or description pattern
-
Include or exclude specific data connections
-
Include or exclude specific data file types
-
Include or exclude specific data file name patterns
-
Include or exclude specific folder name patterns
It is recommended to reload and review the app’s high-level sheets weekly. The data file crawling process can be resource-intensive and is designed to run only once a month by default. You can adjust this frequency if needed.