Why pixel-level RUX beats protocol-only metrics when you size farms and prove changes.
Direct answer: ICA/HDX (and RDP) protocol metrics tell you the session is connected and moving pixels. Real-user experience (RUX) timing tells you when the desktop and published app are actually usable on the glass. For capacity and go-live, you need both—but UX decisions should be driven by on-the-glass measurements from tools like CitraTest VU®, not protocol counters alone.
Side-by-side
| ICA / HDX / protocol | On-the-glass RUX |
|---|
| Sees | Channel, round-trip, connect success | Login-to-shell, app paint, in-session actions |
| Strength | Infra and network signal | What users and CABs care about |
| Blind spot | Slow app that still “streams” | Needs a scripted GUI path |
| Best used for | Tuning transport / gateways | Storm, density, change validation |
Why protocol-only fails capacity debates
A session can be “up” while Epic charts, Outlook, or a line-of-business app paints late. Protocol health will not catch that. Image-based RUX timing will. Same idea applies when comparing HDX to RDP for RDS or cloud multi-session hosts.
Practical recommendation
FAQ
Is HDX Insights enough?
Strong for Citrix transport visibility. Not a full substitute for published-app RUX under load.
Does this apply to RDS / AVD?
Yes—swap HDX for RDP; the glass vs protocol split is the same.
Where does Tevron fit?
CitraTest VU for load; CitraTest APM for continuous RUX.