/
Why Monitoring TM1 System Health is Vital

Why Monitoring TM1 System Health is Vital

As TM1 applications grow in data volume, computational complexity, and user base, monitoring system health over time becomes critical for business continuity. Point-in-time monitoring is not enough — trends and historical comparisons are what provide real insight.

Why Historical Monitoring Matters

Useful health questions require a historical baseline to answer:

  • Is the application as responsive as it was before?

  • Does the server take longer to restart than previously?

  • Are alerts happening with increasing frequency?

  • Is memory consumption growing, and in which cubes?

  • Are user session counts and durations increasing or decreasing?

  • Are processes taking longer to run than they used to?

  • Are certain times of day consistently more problematic?

Without historical data, you cannot answer these questions reliably. Pulse stores all this data over time, making it possible to identify trends and detect degradation before it becomes a serious issue.

The System Summary Report

The System Summary Report consolidates the most important health metrics into a single scheduled PDF report, covering three key areas:

Sessions vs Alerts

Charts the correlation between user session counts and alert events over time. Key things to watch:

  • Whether user sessions are declining (potential adoption problem)

  • Whether alerts increase in proportion to sessions (load-related issues)

Wait Time Analysis

Shows the Top 10 longest wait events and a bar chart of maximum wait time by period. Key thresholds to monitor:

  • Wait time exceeding 60 seconds during working hours

  • Maximum wait time per period trending upward over time

Alerts by Type

Displays the distribution of alert types over the selected period. Key things to watch:

  • Whether total alert volume is increasing

  • Whether the distribution is shifting (new alert types appearing or an existing type increasing)

Scheduling the Report

The System Summary Report can be scheduled to run automatically and distributed to your team via email at a defined interval. For example, configure it to send weekly with the last 7 days of data, so your team always has a current health snapshot without manual effort.

For configuration details, see the System Summary Report article.