On-the-glass monitoring for virtual apps and desktops—continuous checks that match how users work.
Direct answer: Application performance monitoring for Citrix and Microsoft RDS should measure the same path users take—login-to-shell, published-app launch, and in-session UX—around the clock. CitraTest APM® runs synthetic on-the-glass transactions with image recognition and no agents on session hosts. Director, Azure workbooks, and host CPU are necessary; they are not a substitute for what the glass shows.
What “APM” means for EUC
- User-centric — time the desktop and app the way a person sees them
- Always-on — catch morning logon storms and mid-day lag, not only lab events
- Citrix + RDS (+ cloud sessions) — same glass idea across brokers
- Complements load testing — CitraTest VU proves capacity; APM watches production after go-live
APM vs load testing vs dashboards
| CitraTest APM | CitraTest VU | Director / Azure / host metrics |
|---|
| Job | Ongoing synthetic RUX | Capacity / change validation | Infra / control plane |
| When | Production, continuously | Before and during major changes | Always |
| Gap if alone | — | Does not replace 24×7 watch | Green hosts ≠ usable UX |
Signals that matter
- Login-to-shell and first paint of the published app
- FSLogix / profile attach delays visible on the glass
- Morning logon storm vs mid-day density pain
- SLA thresholds on p95/p99, not only averages
Where to go next
FAQ
Is Citrix Director enough for APM?
Director is essential ops telemetry. It does not measure published-app paint the way a user experiences it.
Do I need agents on VDAs or RDSH?
Not with CitraTest APM—synthetics run from outside like real clients.
How is APM different from VU?
VU is load/capacity. APM is continuous production monitoring on the same on-the-glass idea.
CitraTest APM® and CitraTest VU® are Tevron products. Platforms include Citrix, Microsoft RDS, and cloud-hosted sessions.