Monitor current RMM operations
Inspect the loaded device heatmap, prioritize recent alerts, and examine or cancel an active command.
Before you start
- Select an organization with enrolled devices.
- Recent telemetry is needed for health measurements and historical baseline comparisons.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Read the snapshot scope
Open RMM Operations and read the snapshot timestamp and loaded counts for devices, commands, and active alerts. Use Refresh operations for a new read. Follow All endpoints and fleet filters or All active alerts when you need the fuller inventory or alert feed.
Inspect a metric on the device heatmap
Choose the displayed metric and Health or Anomaly mode. Each tile represents a loaded online device; click a tile for its quick panel. Use the heatmap’s paging controls for additional loaded devices.
| Field or control | What to do |
|---|---|
| Health | Inspect the current reported metric on online devices in the snapshot. |
| Anomaly | CPU and RAM compare with loaded observations from the last seven days. Missing baselines remain unavailable. |
| Disk / DEX in anomaly mode | Show current values; do not interpret them as a historical anomaly score. |
| DEX | Shows the complete reported score. Experience applies the organization’s configured DEX thresholds. |
Triage the recent actionable alerts
Review Actionable now, which contains unacknowledged critical and warning alerts from the loaded last-hour subset. Open an alert’s device context, or click Ack after taking ownership. Ack all opens a confirmation for the visible loaded critical and warning alerts; it does not acknowledge every alert in the organization.
What you should see: The recent list reflects the alerts you have acknowledged within its displayed scope.
Inspect a command and its output
Use Command status and Command type to narrow the loaded command list. Open a command row to inspect its details and available output. The pending and running summaries describe this loaded command set; the displayed creation-to-dispatch average is not agent pickup time.
What you should see: You can identify the exact command, target device, and recorded result behind a queue or running count.
Request cancellation or start the next task
For an eligible pending, dispatched, or running command, choose Cancel. Read whether the result says the command was cancelled or only that cancellation was requested, then follow its final status. Use Run a task for new work and confirm the target selection there.
If something doesn’t work
Changing a metric does not change the alert or command list.
Metric and Health/Anomaly controls affect only the heatmap. Use the controls within the command panel or open the Alerts page for alert filters.
Anomaly values are unavailable.
Use Retry baseline if shown. A device needs usable historical CPU or RAM observations; a missing or partial baseline cannot be replaced by a zero value.
An alert is not in Actionable now.
It may be older than the last-hour scope, already acknowledged, informational, or outside the loaded subset. Open All active alerts.