Director is green. Workspace returned 200. The HDX session is connected. The published app is still spinning. That is the Citrix stack problem in one sentence: protocol health and a loaded Workspace URL are not the wait people feel on screen. HDX delivers pixels, not pages – so measuring the stack like a website misses the farm.
Direct answer: Measure the Citrix stack the way Citrix behaves – StoreFront / Gateway / Workspace, then the ICA/HDX session, then a usable shell, then published-app first paint, then in-session click-to-ready – from what users see on the glass. Time each interval with StartTimer – WaitForImage – StopTimer. Do not treat an HTTP check of the Workspace URL, or Director tiles alone, as “Citrix is ready.”
Citrix Virtual Apps and Desktops / DaaS remotes desktops and published apps over HDX (the ICA family). Tevron is not affiliated with Citrix; Citrix and related marks are trademarks of their respective owners. Sister posts: HDX Green Isn’t a Usable Desktop (timing the wait), how to load test Citrix, what is on-the-glass APM, plus RDS and cloud VDI. Method and products: on-the-glass APM, CitraTest VU, and CitraTest APM.
Why a green Director tile is not “the stack is ready”
The Citrix path is a stack, not a single HTTP transaction. Users walk StoreFront or Gateway (or Workspace), negotiate an HDX session, wait for profile and shell, launch a published app, then do work inside that app. Director, Monitor, and HDX Insights are good at session health and channel quality. They are not a stopwatch for “the published app painted” or “the in-session step is ready.”
A Workspace URL can return 200 while HDX has not painted a usable desktop. A session can stream a logon animation or a spinning published-app window and still look connected. Profile attach, GPO, and the line-of-business client sit after HDX is already up. An HTTP generator that hammers the store times the front door, not the farm – because HDX delivers pixels, not pages.
Director green is useful. It is not the same as “the published app is ready.”
The product-language split is the same as Citrix HDX vs real user experience. Host CPU can sit at 40 percent while login-to-shell stretches and the published app paints late. Green protocol tiles do not close that ticket.
Left stack is what Director and Workspace HTTP see. Right stack is what users wait on across the full path. Only the glass stack is Citrix response time as a person experiences the stack.
Which stack steps to time
Write the steps before you pick a tool. Four intervals cover the Citrix stack as it behaves:
- Workspace / Gateway / StoreFront launch path – from credentials submitted (or the Workspace launch) until the store or session-start path is ready on glass. Not “the Workspace URL returned 200.”
- HDX session to usable shell – from session connected until a usable desktop or published-app frame is ready: shell, icons, no logon animation. Not “the broker returned a session” or “ICA RTT is green.”
- Published app first paint – from the icon or Start-menu click until first paint of the business app. Not “the process started on the VDA.”
- In-session click-to-ready – from the click or key that starts the work until the ready state: open record, save, search, switch apps. This is the wait that generates “the app is slow” tickets after everyone is already in session.
Pin the image, VDA, Workspace app, StoreFront or Gateway build, and the published resource. A timer on a moving image is a story, not a measurement.
For capacity work, run a logon storm separately from density. Storm stresses login-to-shell (and the front-door launch path). Density stresses in-session published-app work on hosts that already have users. Blending them hides which interval broke – and hides whether Director stayed green while glass time failed.
Time it like a script, not a feeling
On HDX there is no DOM event that means “done.” The practical signal is the bitmap. The measurement pattern is the same one CitraTest uses on published apps:
- StartTimer when the user action happens – submit, click, or key.
- WaitForImage until a baseline of the ready state is visible: Workspace step, shell, published-app chrome, or in-session ready.
- StopTimer when that image matches.
The recorded interval is click-to-ready for that stack step. Image recognition – and OCR when the ready state is text – is how you know the glass painted, without an agent on the VDA. That is the core of on-the-glass APM.
That pipeline is the same for Workspace launch, HDX shell, published-app open, and in-session work. Change the start action and the ready image. Keep the timer. The narrower sister post on timing the wait uses the same glass method; this post keeps the whole stack in frame.
Stopwatch versus synthetic
A person with a stopwatch can time one published-app open on a quiet morning. That is a demo, not a measurement program. A one-off cannot give a tail, run at the morning rush, hold concurrent sessions while timing an in-session step, or attach a screenshot of the failed state. Means hide the damage until the service desk is already taking calls.
A synthetic does the same StartTimer – WaitForImage – StopTimer path as a real Workspace client, on a schedule or under load, with the same ready baselines across the stack – continuous on-the-glass monitoring, or a Citrix load test when it ramps virtual users.
If you only have a stopwatch, use it to write the acceptance line – then automate it. Example language (schematic only – not a customer dataset or Citrix SLA): Workspace/launch path inside budget at p95; logon-to-shell at p95; published-app open at p95; in-session click-to-ready at p95; fewer than 1 percent of runs hang or miss the ready image.
Continuous watch versus load test
On-the-glass is an idea, not a product SKU. Two jobs share the path:
- CitraTest VU load-tests capacity and change. Freeze the image, walk Workspace / Gateway, then HDX shell, published app, and in-session steps; run storm and sustain as separate shapes; stop at the written budget. See CitraTest VU load testing and the Citrix load-test guide.
- CitraTest APM watches production. The same stack steps, every N minutes, with alerts and screenshots when glass time slips. See CitraTest APM.
The lab answers how many good concurrent stack workflows fit before click-to-ready breaks. The watch answers whether today’s Workspace-to-shell-to-app path is still inside the line. Do not use a load-test generator as your only production monitor. No agents on the VDAs or brokers are required for that path – each virtual user is another Workspace session driving the UI like a person.
What this is not
- It is not a replacement for Director, Monitor, or HDX Insights. Keep those for the remoting path.
- It is not an HTTP soak of the Workspace, StoreFront, or Gateway URL. Keep that for the front door.
- It is not “Director is green, so the published app is covered.” HDX GUIs are pixels users wait on.
- It is not “we have full-stack APM, so Citrix is covered.” Published HDX apps are not only traces.
- It is not a claim about Citrix proprietary internals or unpublished SLAs – only delivered UI readiness on the glass across the stack.
- It is not a promise that last quarter’s number survives a new VDA, FSLogix policy, Workspace build, or a move to Citrix DaaS. Re-time the glass when the image changes.
Take the interval users already wait
Citrix stack response time is click-to-ready on the glass across Workspace / Gateway, HDX shell, published-app paint, and in-session work – not a green Director tile or an HTTP 200 on the Workspace URL. HDX delivers pixels, not pages. Separate logon storm from density. Use a stopwatch only to write the line; use a synthetic to keep it: CitraTest VU under load or change, CitraTest APM on a continuous watch.
When you need that path without agents on the farm – real Workspace client, image and OCR, StartTimer to StopTimer across the stack – schedule a demo. Product pages: on-the-glass APM, CitraTest VU, and CitraTest APM.
Citrix, HDX, ICA, StoreFront, Workspace, and related marks are trademarks of their respective owners. Tevron is not affiliated with Citrix. Names are used for identification only.