Digital Experience Monitoring

Digital Experience Monitoring

Digital Experience Monitoring

Digital Experience Monitoring

Configure and use Cloudmon DEM to monitor business application performance from the end-user perspective, diagnose user-reported issues across device, LAN, WAN, and application layers, and set up alarms and reports.

Overview

Digital Experience Monitoring (DEM) in Cloudmon enables IT teams to track, analyse, and diagnose the real-time and historical experience of end users accessing business applications. DEM captures data from the Cloudmon agent installed on each user's device, measuring performance at every stage of connectivity: the device's own resources, the local LAN, the WAN path to the application including ISP-level metrics, and the application response itself. This five-point analysis gives IT a complete picture of where in the connectivity chain a user's experience is being degraded.

DEM is designed for use on a per-user basis for both on-premises and remote workers, on a per-branch basis for comparing experience across distributed office locations, and for proactive monitoring that surfaces issues before users raise support tickets. Navigate to DEM in the top navigation bar to access all DEM views.

Configuration

DEM monitoring requires two setup steps: adding the business applications to monitor, and associating those applications with a monitoring profile so agents know which applications to measure.

Step 1: Add an Application

Navigate to Settings → Monitoring → Applications and click Add. Fill in the fields as follows:

FieldDescription
NameA display name for the application, such as "Microsoft Teams" or "SAP ERP".
ApplicationThe URL of the application to monitor.
TagsOptional labels to categorise the application for filtering.
SecureToggle to enable a secure connection between the agent and the application. Enable this for HTTPS applications.

Step 2: Associate with a Monitoring Profile

After adding an application, it must be associated with a monitoring profile before any agent will begin measuring it. Navigate to Settings → Configurations → Monitoring Profiles and add or edit a profile. In the Applications section of the profile, click Add and fill in the fields as follows:

FieldDescription
ApplicationSelect the application from the dropdown of all applications added in Step 1.
Application Threshold (ms)The maximum acceptable processing time in milliseconds. This threshold is used to calculate the Apdex score for the application.
PingEnable to collect ping statistics for the application from each agent. When enabled, a Ping Threshold can be configured to define acceptable latency.
TracerouteEnable to collect traceroute data showing the network path from the agent to the application. When enabled, the route is updated every 10 minutes.

Click Save and Associate when editing an existing profile to immediately apply the changes to all agents using that profile. Click Save when creating a new profile. Once associated, all Cloudmon agents assigned to that monitoring profile will begin measuring the application. Navigate to DEM in the top navigation bar to view the data.


InfoNotesNote for MSPs: The same monitoring profile can be associated with agents from different customers. Applications are associated on a customer-specific basis. Even if multiple customers share a monitoring profile, each customer's application will only be monitored by that customer's own agents.

DEM Dashboards

DEM provides two primary dashboards accessible from the navigation bar.

The User Experience Overview Dashboard (Dashboard → User Experience Overview) provides a consolidated summary of DEM metrics across all monitored agents and applications. It contains four sections. The Agents Heat Map displays a heatmap of all monitored agent devices, with each tile coloured by overall user experience score. Clicking an agent opens a detailed summary of that device's performance. The Applications Heat Map shows all monitored applications in a honeycomb view, with tiles coloured by Apdex score. Clicking an application opens its consolidated performance view. The Applications Summary lists all monitored applications with key metrics including agent count, Apdex grade, and processing time. The Geographical View shows the physical locations of all monitoring agents on a map, allowing performance issues to be correlated with geographic location.

The main DEM navigation item provides access to the User Device view, where individual agents and their per-application experience data can be searched and inspected.

Five-Point Analysis

When viewing DEM data for a specific application from a specific agent, Cloudmon displays a five-point analysis of the full connectivity path between the user's device and the application. Each point represents a stage in the connection and is coloured to indicate whether performance at that stage is within acceptable limits. Clicking on any point shows the users or connections impacted at that hop. The five points are:

PointWhat it measures
DeviceCPU usage, memory consumption, and disk usage on the user's device. A device under resource pressure can degrade application performance regardless of network conditions.
LANTraffic in and out on Ethernet, Wi-Fi signal strength, and available Wi-Fi networks. A poor Wi-Fi signal or congested local network can cause packet loss and latency that appears to the user as slow application response.
WANJitter, latency, and packet loss at the ISP level, along with ISP details and the traceroute path between the agent and the application. WAN issues are common causes of intermittent application degradation for remote and branch users.
ISPThe network path between the user's ISP and the application destination. Routing issues at the ISP level, such as a longer-than-expected path to an application hosted at headquarters, are surfaced here.
ApplicationContent type, HTTP status codes, download size, and time-series data for Apdex score and processing time. A degraded application point with healthy network points confirms the issue is server-side.

Common Use Cases

DEM is designed for active troubleshooting as well as proactive monitoring. Below are the most common scenarios where DEM provides immediate diagnostic value:

Wi-Fi signal quality issues: When a user reports an unreachable application, search for their device in DEM. If the LAN point is highlighted as degraded, check the Wi-Fi signal strength and available networks. DEM shows all available Wi-Fi networks in range, enabling IT to advise the user to switch to a stronger network for improved connectivity.

WAN routing path discrepancies: If a user reports intermittent access to an application such as Microsoft Teams, check the WAN point in DEM for that user's device. DEM visualises the traceroute path between the user's device and the application and surfaces cases where the traffic is taking a longer-than-expected route. If a routing issue is confirmed, this can be escalated to the ISP for path investigation.

Branch site-specific application issues: If users from one branch site report slow access to an application while other sites are unaffected, compare the five-point analysis across agents at the affected site versus other sites. A degraded WAN or ISP point specifically at the affected site, such as delayed DNS lookup or higher latency, isolates the issue to that site's connectivity rather than the application itself.

Alarms

Cloudmon supports alarms on five DEM metrics: Apdex score, processing time, device resource usage, WAN latency, and packet loss. To configure alarms for DEM, navigate to Settings → Configurations → Alarm Rules, click Add, select DEM as the entity type, and add triggers for the desired metrics. Each alarm is built around a simple IF/THEN model, where you select a metric, set a threshold, and define what happens when it is breached. Learn more.

Troubleshooting

IssueWhat to check
Application added but no DEM data appearingConfirm the application has been associated with a monitoring profile under Settings → Configurations → Monitoring Profiles. Adding an application alone is not enough. It must be linked to a profile that has active agents assigned to it before any DEM data will flow.
Some agents showing DEM data but others are notVerify that the agents without data are assigned to a monitoring profile that has the application associated. Also confirm the Cloudmon agent is running and reporting on those devices. Navigate to Agents and check the last seen timestamp for the affected agents.
Apdex score is low but application feels fast to the userThe Apdex score is calculated against the Application Threshold set in the monitoring profile. If the threshold is set too low, even acceptable response times will generate a poor Apdex score. Review the threshold value in the monitoring profile and adjust it to reflect a realistic acceptable response time for that application.
Traceroute path is not updatingTraceroute data in DEM updates every 10 minutes when enabled in the monitoring profile. If the path appears stale, verify Traceroute is toggled on in the application's monitoring profile settings. Also confirm the agent has network access to perform traceroute to the application destination without being blocked by a firewall.
    • Related Articles

    • Digital Experience Monitoring (DEM)

      Digital Experience Monitoring Digital Experience Monitoring(DEM) Track, analyse, and diagnose the business application experience of end users from a central location. Cloudmon DEM gives IT teams real-time and historical visibility into how users in ...
    • Agent Vs Agentless Monitoring in cloudmon

      Attribute Agent-based Monitoring Agentless Monitoring – SNMP, WMI, TCP, ICMP Methodology Deploy the Cloudmon Agent on each server that requires monitoring. Cloudmon uses Probes to monitor IP network endpoints and devices in the network such as ...
    • User Experience Overview

      Dashboards User Experience Overview A consolidated DEM dashboard showing the digital experience of all monitored agents and applications. Visualise performance across agents, applications, and geographic locations in a single view. Overview The User ...
    • Monitoring Profiles

      Settings Monitoring Profiles Define polling and reporting intervals, metrics, and process monitoring settings for groups of monitored devices. Monitoring profiles allow consistent configuration to be applied across many devices simultaneously. ...
    • How does the User Experience Trend Chart help in monitoring?

      The User Experience Trend Chart exhibits the average Apdex scores gathered every 10 minutes for an application, representing the overall user experience. However, when you click on a specific agent from Agents > DEM and then an application, the ...