An alert arrives as a ticket with the device attached.
Monitoring and alerting (RMM) is the device monitoring module in The One Stack, the platform MSPs run their whole business on. It checks the health and performance of every managed device against your rules and raises alerts for your team. High and critical alerts open a ticket with the device attached.
Monitoring and alerting (RMM) is part of Endpoints, one of the six systems of The One Stack.
What it does.
Rules for what matters
Built-in monitors cover common conditions such as high CPU, low memory and a filling disk. Custom rules add your own, each with a severity and a duration so a brief spike does not raise one.
Templates with overrides
Apply an alert template to a client or a group, then override it for one client or one device. The standard stays the standard and the exception is on the record.
Offline detection and maintenance windows
A device that misses its check-ins raises an offline alert. A maintenance window suppresses alerts and pauses automations while scheduled work runs, then shows what it held.
One alert per condition
When a condition clears and then returns, the same alert reopens instead of a new one. Alert tuning points out the noisiest rules and suggests adjusted thresholds.
Health and risk by client
A client risk view brings together device health, alert severity and patch compliance. Hardware age, warranty and operating system support dates sit alongside.
Inside monitoring and alerting.
More of the product, screen by screen.
Alert triage
Open alerts are grouped by condition, so a rule that fires again adds to the same row. High and critical alerts carry the ticket they opened, and each one can be acknowledged, resolved or muted from the list.
How it connects.
Monitoring and alerting reads and writes the same record as the rest of the platform.
An alert opens a ticket
High and critical alerts open a ticket in the service desk with the device attached. The alert shows its ticket.
An alert starts a fix
An alert can trigger an automation that runs a script on the device. Destructive actions wait for approval.
Patch status feeds the risk view
Patch compliance from Patching and software is one of the inputs to each client’s risk view.
What THEO does here.
Ask THEO what is wrong with a device and it answers from the device’s telemetry history. THEO also reviews new disk and event log alerts, and runs the fix itself when a runbook covers it.
Questions
Questions about monitoring and alerting
Which alerts open a ticket?
High and critical alerts open a ticket in the service desk with the device attached. Each alert rule also chooses its own routing: email, text message or a ticket.
Can I set different thresholds for one client?
Yes. Templates apply to clients or groups, and overrides apply to one client or one device.
How do I keep scheduled work from flooding the queue?
Set a maintenance window. Alerts for the devices in the window are held, and automations pause until it ends.
Related
Keep going
Start
Run on One.
Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.