What does Digital Experience Monitoring with ZDX mean?
Digital Experience Monitoring (DEM) measures the quality of digital services experienced by the user. Zscaler Digital Experience (ZDX) correlates telemetry from device, network path and application and provides it based on the user and location.
The problem: Each business silo only sees its green section
CPU and WLAN can appear inconspicuous locally, while packet loss at the provider or high response times of a SaaS application slow down the work. Without a common timeline, ping-pong arises between teams.
A single score is also not enough. For a decision, affected users, period, device, web sample, network hops and comparison groups must be considered together.
Several users of a location report poor Teams quality. The service desk first checks range and timing, compares device and network data, and detects whether a local Wi-Fi, ISP, Zscaler, or application issue is more likely.
Diagnostics follow the user path
DEM becomes capable of acting when the score and raw signals are interpreted together.
Device
CPU, memory, processes, system events, and Wi-Fi signal during the problem period.
Local network
Gateway, DNS, WLAN and last mile as separate fault domains.
Cloud Path
Latency and packet loss via hops and providers to the destination.
Application
Web probes, DNS, connection and server times as well as real usage.
Comparison
Differentiate users, locations, departments and time periods against each other.
Workflow
Document findings, owner, ticket handover and success control.
What needs to be checked before making a decision?
- Which users, locations and applications are affected?
- How long has the deviation existed and is it reproducible?
- Which device and Wi-Fi signals change at the same time?
- Where in the network path does latency or packet loss increase?
- Is the application itself affected or only one access path?
- Which measurement confirms the fix?
Definition: DEM telemetry provides strong evidence, but not automatically a complete proof of causation. Edition, activated measuring points and data protection concept determine the available view.
How SourcingBlox brings ZDX into the support process
We combine technical configuration with repeatable triage.
Monitoring Design
Define critical applications, user groups, locations, probes, and success criteria.
Triage Playbooks
Define the test sequence and handoffs for the device, network, Zscaler, and application.
Service Improvement
Regularly evaluate trends, recurring causes and processing times.
Typical mistakes
- Only look at an overall score.
- Don't baseline for sites and critical applications.
- Collect telemetry without adjusting support and escalation paths.
- Automatically treat a temporal correlation as a cause.
Frequently Asked Questions
What distinguishes DEM from classic network monitoring?
DEM starts with the user experience and connects device, path and application data. Traditional monitoring often focuses on individual infrastructure components.
Can ZDX detect SaaS glitches?
ZDX can make application and path deviations visible. Whether the cause lies with the SaaS provider must be assessed based on the available telemetry and comparative data.
Who should use ZDX?
Service desk, workplace, network operations and application owners in particular benefit from a common diagnostic image.
Turn telemetry into a faster support process.
We plan measurement points, triage, escalation and continuous service improvement.
Related Content
Sources and further information
Measured values and functions depend on the edition, client configuration and activated modules and must be checked in the specific tenant.