SysTrack scores 13 health impact categories by default. The following table lists the metrics, default thresholds, what each category measures, and example causes for each category.
NOTE: Although the default values reflect common customer environments, they may not fit all scenarios. Observe your environment behavior during baselining and adjust thresholds as needed to reflect operating system differences and workload patterns. For example, customers running Windows 11 often increase the virtual memory commit ratio from 0.90 to 0.95 to align with more aggressive memory and page file management.
Category | Metric | Default | Description | Example Causes |
|---|---|---|---|---|
CPU |
|
| CPU use or activity hinders productivity. | Underpowered CPU, too many applications running, excessive CPU consumption, applications spawning multiple CPU threads, outdated applications |
Memory | Memory Available | Less than 20% (agents on version 10.11 and earlier use an absolute byte threshold instead) | Memory availability hinders productivity. | Insufficient RAM, too many applications running, applications that consume excessive memory |
Disk |
| Counted only when disk operations exceed 5 IOPS (input/output operations per second), and one of the following is also true: Queue Length greater than 1; Queue Time greater than 10 ms; Service Time greater than 20 ms; Disk Time greater than 80%; Transfer Time greater than 20 ms | Disk availability or activity hinders productivity. | Applications using excessive IOPS, mechanical or low-speed hard drives, applications saturating the drive with reads and writes |
Network |
|
| Network card utilization or activity hinders productivity. | High network utilization, excessive packet retransmits, poor Wi-Fi signal affecting connection stability and throughput |
Latency |
|
| Latency to external locations hinders productivity. | Default gateway, home drive, session protocol round-trip time |
Startup |
|
| Application or session startup hinders productivity. | Slow application load, slow session logon |
Virtual Memory | Commit Ratio | Greater than 90% (Windows only) | Virtual memory usage hinders productivity. | Insufficient physical memory, memory-intensive applications |
Virtual Machine |
|
| Virtual machine host problems hinder VM productivity. | Host memory overcommitment, host CPU contention |
Software Install | Installation Process Active | A software installation process uses CPU while it has focus, counted at most once every 60 seconds (Windows only) | Software installation hinders user activity. | Install events |
Software Update | Update Process Active | A software update process uses CPU while it has focus, counted at most once every 60 seconds (Windows only) | Software or operating system updates hinder user activity. | Update events |
Events | Windows Event | An alarm triggered on an event at level Error, Warning, or Critical (Windows only) | Key event errors indicate user activity impact. | Critical, error, or warning events in the event logs, if configured to be captured |
Faults |
|
| An application or the operating system crashes. | Application crash, BSOD, kernel panic |
Hardware | Hardware Interrupt Rate | Greater than 10% | Hardware or driver interrupts take resources from user activity. | Interrupt rate |
SysTrack records application hangs, but they do not count as Faults.
Changing Thresholds by Role
SysTrack uses the same default thresholds for every role. You can set a different threshold for a role (see Health), or, for SysTrack On-Premises, in the SysTrack Deployment Tool, under Configuration > Global Configuration Items > Health.
A custom threshold that you set for a role takes precedence over the default and is not overwritten when SysTrack updates its defaults. The exception is a custom Available Memory threshold set in bytes: agents on version 10.12 and later ignore it and use the percentage threshold (Limit Memory Percentage) instead.
Windows and macOS or Linux Differences
The macOS and Linux agents do not measure several categories that the Windows agent measures: Events, Software Install, Software Update, Virtual Memory, Virtual Machine, and the two Startup metrics. They also do not measure network retransmit rate.
Health and Memory Threshold Updates in SysTrack 10.12
After 10.12 is applied to your cloud environment, SysTrack applies the new thresholds to all agents.
Wi-Fi signal strength affects health when it falls below the configured threshold. You can configure this threshold per role before updating agents.
Memory thresholds now use a percentage for 10.12+ agents and an absolute value for 10.11 and older agents.
Health scores reflect the new thresholds, which may change overall estate health and per-device health scores.
If you upgrade from 10.11 or earlier: to keep your own thresholds instead of the 10.12 defaults, set custom values per role before you upgrade (see Health). For memory, set Limit Memory Percentage.
The following table lists the updated default health thresholds and their new values.
Category | Metric | Old Value | New Value |
|---|---|---|---|
CPU | CPU Percentage | >95% | >90% |
Hardware | Hardware Interrupt Rate | >25% | >10% |
Latency | Gateway Latency | >5 ms | >75 ms |
Home Directory Latency | >25 ms | >100 ms | |
Session Latency | >100 ms | >200 ms | |
Memory | Memory Available | <50,000,000 bytes | <20% |
Network | Retransmit Rate | >10% | >5% |
Utilization | >30% | >70% | |
Wi-Fi Signal Strength | Not applicable | <50% | |
Virtual Machine | Ready Time | >10% | >5% |