Every IT team has lived this scene: the monitoring wall is fully green and a user is standing at the desk saying the computer is unusable. Both are telling the truth — they are just measuring different things.
Normal monitoring answers is it up. DEX answers is it usable. A file server at 40 percent CPU, a switch with no errors and an antivirus console showing all green can still deliver a miserable morning to the person whose PC takes four minutes to log on, freezes twice before lunch and crashes Excel every afternoon. Those events are invisible to uptime monitoring because nothing is down — everything is merely slow, unstable or annoying. DEX exists to measure exactly that gap.
👆 Green on the left, painful on the right — both true at the same time (example figures)
A service can be up and still be effectively broken for the user. The printer service runs, but the PC takes 90 seconds to open the print dialog. The mail server answers, but Outlook freezes for 20 seconds on every search. Availability monitoring was built for servers in a rack, where up or down is most of the story. On an endpoint, the story is waiting: waiting to boot, waiting to log on, waiting for an app to respond. DEX measures the waits.
The responsiveness metrics are the ones users feel in their bones: boot time from power button to a usable desktop, logon time from entering a password to actually working, and input delay — the lag between doing something and the machine responding. When these stretch, users describe the PC as "slow" even if its CPU is bored. No classic ping or service check will ever report a four-minute logon as a problem. DEX reports it as a headline number.
There is a sadder blind spot. When an application crashes every day, users report it twice, then stop reporting and just live with it — saving work every few minutes, restarting the app without telling anyone. Your ticket count goes down while the experience gets worse. DEX records application crashes and system crashes as events, immediately when they happen, so silent suffering becomes visible data. Some of the worst PCs in an office are the ones with zero tickets.
Disks fill up gradually. Battery health fades month by month. A startup list grows one updater at a time. None of these trip an alarm in classic monitoring until the day something finally breaks. DEX trends the underlying metrics — disk space, battery health, device age, performance over time — and flags threshold crossings early, while the fix is still a small job scheduled at a calm hour instead of an emergency at month-end.
With experience data, conversations change. Instead of "the PC feels slow" versus "our dashboard says fine", both sides look at the same numbers: logon time is up 80 seconds since the new security agent rolled out, and 60 similar PCs show the same jump. The argument ends and the fixing starts. That is the real product DEX sells — not more charts, but an end to opinion-based IT on endpoints.
The video shows the experience metrics side by side with classic monitoring — watch it to see which of your daily complaints suddenly become measurable.
▶️ Watch Full VideoThe raw ingredients overlap, but the question differs. Classic monitoring asks whether a machine is up and loaded. DEX asks whether the person using it waits, freezes and crashes — boot time, logon time, input delay, app crashes and battery health, combined into an experience score per device.
Because slowness is usually waiting, not computing — slow storage, a bloated startup, logon scripts and policies applying one by one, or an app that hangs rather than works hard. CPU graphs miss all of that; responsiveness metrics catch it.
No. DEX is endpoint experience telemetry. Server, network and application monitoring answer different questions and remain necessary. DEX completes the picture on the device side; it does not substitute the rest.