Understanding the Statistics controls
Figure 1: Statistics controls
- Host — Selects which WebReports server to review. Choose a specific host to see its workload and process-resource information. All Hosts combines report activity from every host with retained statistics, but process-specific memory and CPU information is unavailable because those measurements belong to individual WebReports processes.
- Process — Appears after selecting a specific host. All PIDs combines statistics from the WebReports processes that ran on that host, including earlier processes from application restarts. Selecting a particular PID limits the page to that individual process and its lifetime.
- Timeline — Selects the start and end of the period used by the summary cards, charts, and Activity table. The default period is the most recent 30 minutes. Moving the selected range away from the current time changes the page from Live to Historical mode.
- Live — Indicates that the selected period ends at the latest available statistics and the page is automatically refreshing. The page refreshes every 30 seconds.
- Historical — Indicates that an earlier period is being reviewed. Automatic refresh pauses so that the selected historical range does not move.
- Refresh — Immediately reloads the selected host, process, time period, cards, charts, and activity records.
Workload and resource peaks
The Workload & resource peaks (relative) timeline is an overview of retained activity. It helps administrators locate periods of heavy report activity or increased resource use before selecting a more precise time range.
Figure 2: Workload and resource peaks
The timeline combines:
- Waiting — Queue & Download and Scheduler reports waiting to begin.
- Running — Queue & Download, In-Memory, and Scheduler reports executing.
- Completed — Reports completed during each recorded interval.
- Failed — Reports that failed during each recorded interval.
- Memory — Working-set memory used by the selected WebReports process.
- CPU — CPU used by the selected WebReports process.
The peaks are displayed on relative scales. Their height is useful for locating spikes, but it should not be used to compare the absolute size of CPU, memory, and workload values. Hover over the timeline to see the recorded values.
Shaded gaps labeled No data recorded or Process not reporting indicate periods without statistics samples. A gap can occur when WebReports was stopped, restarting, unable to persist statistics, or the selected process was no longer running.
Queue & Download card
The Queue & Download card represents reports submitted to the background Queue & Download workload. This includes queued report requests and reports being prepared for download.
Figure 3: Queue & Download statistics
- Active / max — The first number is the number of Queue & Download reports currently executing. The second number is the configured maximum number of Queue & Download worker threads. Additional reports wait when all workers are occupied.
- Waiting / capacity — The first number is the number of submitted Queue & Download reports that have not started executing. The second number is the configured queue capacity. Capacity limits waiting work; it does not increase the number of reports that can execute simultaneously.
- Completed / selected period — The number of Queue & Download reports that finished successfully during the selected timeline period.
- Failed / selected period — The number of Queue & Download reports that finished with a failure during the selected timeline period.
In-Memory — Run Report card
The In-Memory — Run Report card represents interactive reports generated immediately when a user selects Run Report. These executions are monitored separately from the Queue & Download worker queue.
Figure 4: In-Memory — Run Report statistics
- Active now — The number of interactive Run Report requests currently executing.
- Completed / selected period — The number of interactive reports that finished successfully during the selected period.
- Failed / selected period — The number of interactive reports that failed during the selected period.
This card does not display waiting, capacity, or maximum-worker values because interactive Run Report requests are not processed through the Queue & Download or Scheduler worker queues.
Scheduled Reports card
The Scheduled Reports card represents reports started by the WebReports scheduler.
Figure 5: Scheduled Reports statistics
- Active / max — The first number is the number of scheduled reports currently executing. The second is the configured maximum number of scheduled reports that can run concurrently.
- Waiting / capacity — The first number is the number of scheduled reports waiting to execute. The second is the configured scheduled-report queue capacity.
- Completed / selected period — The number of scheduled reports that finished successfully during the selected period.
- Failed / selected period — The number of scheduled reports that failed during the selected period.
A consistently high active count near the maximum indicates that the configured scheduler threads are fully utilized. A growing waiting count indicates that scheduled work is arriving faster than the available workers can process it.
Report activity charts
The three charts below the cards show activity within the selected timeline period:
Figure 6: Report activity charts
- Queue & Download — Peak waiting reports, peak running reports, and completed reports per time bucket.
- In-Memory — Peak running interactive reports and completed reports per time bucket.
- Scheduler — Peak waiting reports, peak running reports, and completed reports per time bucket.
“Peak waiting” and “Peak running” show the highest observed concurrency within each statistics bucket. “Completed” shows how many reports finished within that bucket.
The bucket duration appears above the charts. It normally matches the configured Statistics sampling interval, but WebReports can combine samples into larger buckets when displaying a long period or aggregating multiple processes. Failures are shown in the summary cards, peak timeline, and Activity table rather than as a separate series in these three charts.
Activity table
The Activity tab lists individual report executions associated with the selected host, process, and timeline. It includes reports that overlapped the selected period, even if they began before the period started.
Figure 7: Statistics Activity table
| Column | Description |
|---|---|
| Report | Name of the report definition. |
| Report desc | Description assigned to the report definition. |
| Connection | Connection Profile used to retrieve the report data. |
| User | Username associated with the request. The user ID may be shown when a username is unavailable. |
| Type | Action performed, such as Run Report, Queue, Download, or a scheduled action. |
| Workload | Execution path: Queue & Download, In-Memory, Scheduler, or Completed Report. |
| Status | Current or final state: Waiting, Running, Completed, Failed, or Interrupted. |
| PID | ID of the WebReports process that executed the report. Hovering over it displays the associated host. |
| Start | Date and time execution began. It remains blank while a report is waiting. |
| End | Date and time the execution completed or failed. Running items display “Running.” |
| Duration | Waiting time for a waiting item, elapsed execution time for a running item, or total execution time for a finished item. |
| Dataset size | Size of the serialized result dataset before compression or encryption. It may be unavailable when no result size was captured. |
| CPU | Highest observed CPU percentage for the shared WebReports process while the report was running. This is not CPU attributable exclusively to that report. |
Activity statuses
Figure 8: Activity statuses
- Waiting — Submitted but not yet executing.
- Running — Execution has started and has not finished.
- Completed — Execution finished successfully.
- Failed — Execution ended unsuccessfully.
- Interrupted — An item remained recorded as Waiting or Running, but its WebReports process stopped reporting. This commonly indicates an application stop or restart before a final status was recorded.
The Completed Report workload can appear when WebReports must reconstruct a previously stored report because its dataset is no longer present in the per-user cache. This activity appears in the table but is intentionally excluded from the Overview workload cards and charts.
Shared WebReports process performance
Figure 9: Shared WebReports process performance
- Working-set memory — Displays the physical working-set memory currently used by the selected WebReports process. When available, it is shown alongside the total memory available to WebReports. The accompanying chart shows working-set history across the selected period.
- CPU — Displays CPU use for the selected WebReports process. The value is normalized across the server’s logical processors and can range from 0% to 100%. The first sample may display Collecting… because CPU requires two samples to calculate. Unsupported or unavailable telemetry displays Unavailable.
Memory and CPU belong to the shared WebReports process. Multiple reports, web requests, hosted services, and other WebReports operations can contribute to these measurements, so they should not be interpreted as resource use caused by one report.
Configuration note
Statistics collection is controlled under the WebReports Statistics settings:
Figure 10: WebReports Statistics settings
- Statistics are enabled by default.
- The default sampling interval is 30 seconds and can be configured from 5 to 3,600 seconds.
- Statistics are retained for 7 days by default and can be configured from 1 to 30 days.
- The page’s 30-second automatic refresh is independent of the configured sampling interval.
Comments
0 comments
Please sign in to leave a comment.