Also published on the product site: overnight-shift-watch-citratest-apm.aspx
CitraTest APM continuous monitoring for after-hours and unattended shifts – same WaitForImage contract, SLA alerts when the glass path slips and the NOC is empty.
Direct answer: CitraTest APM® keeps an on-the-glass watch running overnight and across unattended shifts by scheduling the same WaitForImage + StartTimer/StopTimer path that daytime ops already trust – then paging when an SLA limit breaches or an iteration fails. Playback uses real mouse and keyboard on Citrix, Microsoft RDS, Azure Virtual Desktop, browsers, and thick Windows clients. No CitraTest agents on production session hosts for the glass path. The dashboard can be empty; the watch still has to be honest.
At 02:17 the workbook is still green. Host CPU is calm. The gateway answered. Nobody is staring at those tiles – and that is normal for overnight, weekend, and thin-NOC coverage. The question is not whether a chart was watched. The question is whether tonight’s login-to-shell, published-app first paint, or in-session transaction still landed on screen inside the SLA your shift already agreed to.
An overnight shift watch answers that without inventing a second definition of success. Same glass path. Same timers. Different operational assumption: eyes may be elsewhere, so the alert has to carry the proof.
Daytime eyes vs overnight witnesses
Daytime monitoring often leans on people: someone notices a pie chart turn, opens a report, correlates a ticket. After hours that habit breaks. Batch windows, maintenance, quiet hours, and follow-the-sun handoffs all leave stretches where the only reliable witness is a scheduled synthetic that still drives the client the way a person would.
Control-plane green does not fill that gap. Director, Azure workbooks, and gateway HTTP checks remain useful for brokers and hosts – they do not time whether the business screen appeared. Related: Director Watches Brokers. APM Watches the Screen.
Illustrative / method diagram – not Tevron customer results. Overnight coverage still needs glass timing, not only broker health.
Same glass contract – even when the floor is dark
CitraTest APM does not switch measurement models at midnight. Per User Guide / Quick Start guidance, the overnight Scenario uses the same contract as any continuous watch:
- Scripts encode the workflow on a Windows desktop.
- Playback sees the UI with bitmap images (and OCR when text is dynamic).
- Playback acts with real mouse and keyboard.
- WaitForImage synchronizes and verifies expected screen state before the next step.
- StartTimer / StopTimer capture on-screen response: StartTimer immediately after the initiating action; StopTimer immediately after WaitForImage confirms completion.
Prefer static bitmaps for sync cues that do not change. Reserve OCR for values that are unknown ahead of time. OCR is not a wait/sync – confirm readiness with image functions first, then read or assert dynamic text if needed. Keep baseline images small and unique; match display properties between capture and playback machines so "image not found" is a real delay, not theme drift that only shows up on the quiet shift.
Illustrative method diagram – not customer results. That pipeline is the measurement contract inside every published overnight monitor.
Schedule the watch for unattended hours
Building the script is not enough. After-hours coverage needs operational shape in the APM Web Console – the same Publish → Scenario → SLA lifecycle described in the continuous-watch guide, applied to overnight cadence:
| Piece | Overnight / unattended focus |
|---|---|
| Publish | Send the exe and baseline images to the APM Web Console so agents run a known version – not a laptop copy someone forgot to update before the weekend. |
| Scenario schedule | Prove the path on the interval the shift actually needs (batch window, every N minutes overnight, tighter for critical transactions). Quiet hours still need successive iterations – not a single 09:00 check. |
| Groups / monitors | Attach the timers that matter after hours: login-to-shell, app first paint, and the one or two in-session steps the next morning cannot invent. |
| Playback endpoints | CitraTestAPMAgent machines with access to the real client path – Citrix Workspace, RDS/AVD client, thick client, browser – ready before the floor empties. |
| SLA + alerts | Score up to four response-time limits per Monitor/Timer. Page when a glass step breaches or an iteration fails; attach failure screenshots as the first evidence pack for whoever is on call. |
Availability for summary reporting can still track successful iterations (Monitor Required Availability) separately from response-time bands. Failover agents can stand by when a primary is silent for an extended period; they still need Group/Scenario membership so the overnight watch does not depend on a single quiet desktop.
For the full fleet lifecycle – Publish, Scenario membership, SLA scoring – see Publish → Scenario → SLA: Running CitraTest APM as a Continuous Watch. This article is the after-hours operational question that lifecycle answers when nobody is looking.
Illustrative fleet flow based on the Quick Start APM Web Console chapter – not customer results.
Alerts replace eyes – screenshots replace guesswork
When the dashboard is empty, the alert is the handoff. Design it that way:
- Name timers after moments of truth – first useful pixel / login-to-shell, app or workspace ready, key transaction ready – not after protocol hop labels.
- Set SLA bands from agreed operational limits – what the shift already treats as too slow – then let overnight iterations report whether the path still meets them.
- Treat failure screenshots as first evidence – on-glass proof of where the path stopped, so on-call does not reopen a green workbook and stop there.
- Do not invent accuracy percentages or fictional ROI – the value of the overnight watch is honesty across successive iterations.
Illustrative method diagram – not customer results. Geo shapes are example scenario layouts, not benchmarks.
Hygiene for unattended iterations
Quiet-shift failures are often environment debt, not mysterious outages. Keep the overnight watch trustworthy:
- Restore a clean desktop between iterations so leftover windows do not poison the 03:00 run.
- Publish cleanup scripts as standalone monitors when residue would strand the next schedule.
- Use script versioning for phased rollout – avoid assigning conflicting versions of the same script to one agent before a long weekend.
- Match display contracts – resolution, color depth, theme, font smoothing – between capture and playback so night-only "image not found" noise stays rare.
If you already sized concurrency with CitraTest VU, reuse the same visual definition of success in APM. VU answers "how many?" under load; APM answers "is it still true this hour – including the hours nobody is watching?" Related method posts: Control Plane ≠ Farm (how to build the automated tests), Profile the User Journey, Then Scale the VUs, What is on-the-glass APM?.
Closing: keep the quiet hours honest on the glass
Overnight Shift Watch is not a different product mode. It is CitraTest APM continuous monitoring under the assumption that the dashboard may be empty – encode the path with WaitForImage and timers, publish it, schedule it across playback endpoints, and page when the steps users feel breach SLA. Infrastructure metrics still matter for hosts and brokers. They do not replace a scheduled proof that the business screen appeared on time while nobody was looking.
FAQ
What is an overnight shift watch in CitraTest APM?
An overnight shift watch is a scheduled glass-level Scenario that keeps proving login-to-shell and key in-session steps while the NOC is thin or empty. CitraTestAPMAgent playback machines run WaitForImage-timed paths on a schedule; SLA limits and failure screenshots alert when the business screen is late – without requiring someone to stare at a dashboard.
How do overnight APM watches differ from daytime dashboard monitoring?
Daytime often assumes eyes on charts. Overnight and unattended shifts need the watch itself to be the first witness: scheduled iterations, SLA response-time bands, and alerts with on-glass proof. The measurement contract does not change – WaitForImage sync and StartTimer/StopTimer – only the operational assumption that nobody may be looking.
How should timers be placed for after-hours glass scenarios?
Place StartTimer immediately after the initiating action. Confirm readiness with WaitForImage (prefer static bitmaps for sync). Place StopTimer after that wait succeeds. OCR may read or assert dynamic text afterward; OCR is not a wait/sync.
Do overnight watches require agents on production session hosts?
No. For the glass path, CitraTestAPMAgent runs on playback machines with Windows access to the client path. No CitraTest agents are required on production session hosts.
How does this relate to Publish → Scenario → SLA?
Publish → Scenario → SLA is the fleet lifecycle that turns a glass script into a continuous watch. This overnight article is the operational question that lifecycle answers after hours: keep proving the path and page someone when the screen is late, even when the dashboard is empty.
When you need that glass path without agents on production session hosts — schedule a demo. Product pages: CitraTest VU, CitraTest APM, and the Tevron.com blog.
Citrix, HDX, ICA, StoreFront, Workspace, Microsoft, Remote Desktop Services, RemoteApp, Azure Virtual Desktop, and related marks are trademarks of their respective owners. Tevron is not affiliated with those vendors. Names are used for identification only.