How Application Health Is Calculated

Application Health Monitoring allows administrators to easily track how applications are performing without relying on external tools. This capability provides detailed analytics based on application-specific latency thresholds, which indicate whether performance is Good, Fair, or Poor. By comparing real-time latency against these thresholds, administrators can quickly identify performance issues and take corrective action.

HPE Aruba Networking Central calculates Application Health based on the end-to-end latency reported by Gateways (any AOS-10 version) for all TCP flows going through the network. These values are then contrasted against a set of application-specific thresholds (resulting from research done by HPE Aruba Networking). Application Health and UXI status are calculated based on performance trends observed over defined time windows, such as the last 3 hours, 1 day, or 7 days. The UXI status is not a single point‑in‑time metric. It reflects aggregated health signals collected throughout the selected period to provide a more accurate and meaningful representation of the application's overall behavior.

Table 1: Application-specific Thresholds

Application Name	Good	Fair	Poor
Google Meet	Latency < 25ms	25ms < Latency < 50ms	Latency > 50ms
Jabber	Latency < 100ms	100ms < Latency < 200ms	Latency > 200ms
Teams	Latency < 100ms	100ms < Latency < 200ms	Latency > 200ms
Zoom	Latency < 75ms	75ms < Latency < 150ms	Latency > 150ms
Generic VoIP	Latency < 75ms	75ms < Latency < 150ms	Latency > 150ms
Generic SaaS	Latency < 200ms	200ms < Latency < 400ms	Latency > 400ms
Generic Internet	Latency < 250ms	250ms < Latency < 500ms	Latency > 500ms

Application Health Monitoring in Site Context

HPE Aruba Networking Central analyzes the latency of TCP flows for a specific application over the last fifteen minutes for every user. The latency of each flow is measured, which can number in the thousands in a large site.

Consider an example of Microsoft Teams with 1000 flows in 15 minutes. Assume the latency distribution is as follows:

• Below 100 ms—Good (200 flows)

• Between 100-200 ms—Fair (100 flows)

• Above 200 ms—Poor (700 flows)

The composite Application Health bar displays green, yellow, and red segments based on these thresholds. A higher number of flows exceeding 200 ms results in a larger red segment, indicating poor application health.

Application Health Monitoring in Client Context

HPE Aruba Networking Central analyzes all flows for a specific application for a single user in the last 15 minutes. The composite Application Health bar displays green, yellow, and red segments based on the latency thresholds.

Requirements to Measure Application Health

The minimum hardware and entitlement for application performance monitoring are listed below:

Table 2: Minimum Requirements for Application Health Insights

Device Type	Hardware Support	Software Support	Licensing Tier
AOS-10 Access Points	AP-7xx Series and above	AOS-10.8.0 or higher	Advanced
AOS-10 Gateways	7000 Series 7280 Series 9000 Series 9100 Series 9200 Series	AOS-10.4.0.0 or higher	WLAN Advanced or higher SD-Branch Foundation or higher