Define polling and reporting intervals, metrics, process monitoring, and DEM application settings for groups of monitored devices. Monitoring profiles allow consistent configuration to be applied across many devices simultaneously.
A monitoring profile defines how frequently data is collected from monitored devices (polling interval), how often that data is reported (reporting interval), which specific metrics are collected, whether Docker container monitoring is enabled, and which DEM applications are associated with the profile.
After a new agent is discovered by the Cloudmon controller, it is automatically associated with the default monitoring profile. Custom profiles can be created for different device types, criticality levels, or frequency requirements. Navigate to Settings → Configurations → Monitoring Profiles and select the Agents tab to view and manage all agent profiles.
| Field | Description |
| Name | A descriptive name for the profile, such as "High Availability Server" or "DEM - WiFi Usecase". |
| Polling Interval | How frequently the agent collects data from the device. Select a shorter interval for critical, high-frequency monitoring or a longer interval for low-priority devices. |
| Reporting Interval | How frequently the agent sends collected data to the Cloudmon controller. Adjust based on bandwidth and data retention requirements. |
| Processes — Docker Containers | Checkbox to enable Docker container monitoring. When enabled, the agent collects metrics for all running Docker containers, including CPU, memory, network I/O, and block I/O. Refer to the Docker Host Monitoring section for full details. |
| Monitors | Multi-select field to choose which system metrics the agent collects. Available metrics include CPU usage, CPU load averages, CPU user/kernel/nice/idle time, CPU interrupts, CPU temperature, per-core CPU usage, memory usage, memory buffer cache, memory swap, filesystem usage, filesystem read/write rates, disk IO read/write requests, disk IO read/write wait time, transmit rate, receive rate, and battery percentage. Select only the metrics required for your monitoring use case to reduce agent overhead. |
Digital Experience Monitoring (DEM) application settings are configured within monitoring profiles. After creating an application under Settings → Monitoring → Applications, it must be associated with a monitoring profile before any agents will begin collecting DEM data. Adding an application alone is not sufficient; the association step is required.
To add an application to a monitoring profile:
Add Application Modal Fields:
| Field | Description |
| Application | Dropdown menu listing all applications added in Settings → Monitoring → Applications. Select the business application to monitor from the end-user perspective. |
| Application Threshold (ms) | The maximum acceptable processing time in milliseconds. This threshold is used to calculate the Apdex score for the application. If the application responds faster than this threshold, user experience is considered satisfied. If it exceeds the threshold, the Apdex score declines. A higher threshold means more lenient Apdex scoring. |
| Ping | Checkbox to enable ping statistics collection from each agent to the application. When enabled, a Ping Threshold field appears. Ping data contributes to the LAN and WAN analysis in the five-point DEM view and helps identify network latency issues separate from application performance. |
| Traceroute | Checkbox to enable traceroute data collection, showing the full network path from the agent to the application. When enabled, the route is updated periodically. Traceroute is essential for diagnosing WAN routing issues, ISP-level problems, and identifying exactly which hop is introducing latency or packet loss. |
Applications Table Columns: After adding applications, they appear in the Applications table within the profile, with the following columns:
When associating with a parent group, you can optionally include all sub-groups. This allows bulk association across an entire site or department hierarchy without needing to associate each sub-group individually.
To create a variation of an existing profile, click the clone icon next to the profile in the list. A copy of the profile is created which can be edited independently. Cloning is useful for creating device-type-specific or criticality-specific variations of a base configuration without starting from scratch.