DEX Application Performance Metrics
The BigFix DEX solution leverages DEX metrics to monitor application health, detect anomalies, and assess their impact on endpoint user experience.
Data collection:
- Metrics are collected locally by the BigFix Scanner running as a background service on every managed endpoint.
- Metrics are collected by using Microsoft Windows exposed APIs on Windows endpoints.
- On macOS based endpoints, metric collection leverages native interfaces and system utilities to retrieve performance and health data.
The metrics are sampled every 30 seconds at the endpoint and aggregated into one single value every Aggregation Time Interval (ATI) of 5 minutes. Each ATI will contain 10 metric values. For each metric, the Average value is shown in the UI within the ATI.
Metric classification:
- Scorable: Used as input to our scoring system to classify the DEX Experience
- Non-scorable: The corresponding metric is informational, as they are not used as input to our scoring system. However, they are reported to provide a detailed view of the endpoint status at any time.
Core Metrics Reference
Below is a list of the DEX Application metrics currently available and their classification as Scorable/ Non-scorable based on Windows-Only Metrics, macOS-Only Metrics, and Cross-Platform Metrics (Both Windows and macOS).
| Leaf score | Metric description | If scorable | Platform supported |
|---|---|---|---|
| Desktop Reliability Application |
CPU usage (percentage) Per-Application CPU Usage: The percentage of CPU processing capacity consumed by a specific application (parent process + all child processes) averaged over ATI. To monitor performance impact on the end-user experience and help the remediation. CPU usage applies to a specific application version. |
Non-Scorable | Windows Mac OS |
| Memory Usage (MB) Per-Application Memory Usage: The amount of physical RAM allocated to an application (parent + child processes) averaged within the corresponding ATI. To monitor performance impact on the end-user experience and help the remediation. Memory usage applies to a specific application version. |
Non-Scorable | Windows Mac OS |
|
|
Killed after Freeze (Number of events) Application Freezes: Tracks when monitored applications stop responding on Windows and macOS by parsing OS-generated hang logs (Event ID 1002 on Windows, .hang reports on macOS). Freeze is reported as event per a specific application version. |
Scorable | ||
|
Crashes (Number of events) Application Crashes: Tracks when monitored applications unexpectedly terminate on Windows and macOS by parsing OS-native diagnostic logs (Event ID 1000 on Windows, .crash reports on macOS). Crash is reported as event per a specific application version |
Scorable | Windows Mac OS |
|
|
Unresponsiveness (percentage) Application Responsiveness (Windows-only): Tracks the user interface responsiveness and active session health of monitored applications on Windows endpoints. Evaluated every ATI by executing synthetic probe sessions using the native Windows IsHangAppWindow API. The metric is reported as a Failure Ratio percentage, calculated as the number of failed (hung) session probes over the total probes executed (within the ATI sampling window for a specific application version. It requires a specific executable installation (bf_us_scan.exe). |
Non-Scorable | Windows Mac OS |
|
|
Response time (ms) Application Response Time: Measures the network latency and transport layer responsiveness between the monitored endpoint and the application backend. Evaluated every 5 minutes by calculating the average Smoothed Round-Trip Time (SRTT) derived from active TCP connections. The metric is aggregated and reported as an average duration (in milliseconds) within the ATI sampling window for a specific application version. |
Non-Scorable | Windows Mac OS |
|
|
TCP failure ratio (percentage) TCP Connection Failure Ratio: Measures the reliability of transport layer network sessions between the endpoint and the application backends. Evaluated during each Aggregation Time Interval (ATI) by tracking all outbound TCP connection attempts initiated by the monitored application. The metric is reported as a Failure Ratio percentage, calculated as the number of failed TCP establishment attempts over the total connection attempts initiated within the ATI for a specific application version. |
Scorable | Windows Mac OS |
|
|
TCP Active Connections (number of connections) TCP Active Connections: Tracks the transport layer concurrency and network activity generated between the endpoint and the application backends. Evaluated during each Aggregation Time Interval (ATI) by measuring the number of concurrent established outbound TCP sockets owned by the monitored application. The metric is reported as a peak count, within the ATI for a specific application version and contributes to calculate the weight of TCP failure ratio anomalies and it is shown in the same window |
Non-Scorable | Windows Mac OS |
|