Configure Alert Thresholds
Set CPU, memory, and disk thresholds that trigger alerts.
How alerting works
An alert template is a set of rules applied to devices of a given type. Each rule watches one metric and fires when it crosses a threshold you set. A template holds as many rules as you need — that is how you get a warning level and a critical level: two rules on the same metric with different thresholds and severities.
Creating a template
- Go to Monitoring → Alert Templates and click New Alert Template.
- Name it and pick the device type it applies to — Servers, Workstations, Laptops, Routers, Switches, Printers, or Generic.
- Add a rule:
- Metric — around fifty are available, grouped by CPU, memory, disk, network, temperature, system, GPU, power, printer, application and security. Examples: CPU Usage (%), Disk Free Space (GB), SSL Certificate Days Remaining, Toner Black (%), Battery Level (%).
- Operator — greater than, greater than or equal, less than, less than or equal, or equal to.
- Threshold — the number to compare against.
- Severity — info, warning, or critical.
- Auto-create ticket — tick this to raise a ticket when the rule fires.
- Repeat for each condition, then save.
The alert message is built for you from the metric, operator and threshold, so the alert reads the same way every time.
What happens when a rule fires
The alert appears under Monitoring → Alerts, and an in-app notification is raised. Repeat notifications for the same device and condition are suppressed for an hour, so a device that is flapping does not bury everything else.
If the rule has auto-create ticket enabled, a ticket is raised against the device and goes through your normal queue, assignment and SLA. Those tickets close themselves — when the underlying condition clears, Plenix resolves the ticket it opened, so nobody has to tidy up after a disk that filled and then emptied.
Note: a template has no recipient list — there is nowhere to nominate who gets emailed or texted for a given rule. Alerts land in the notification centre at Platform → Notifications for everyone who can see the device. If a specific person needs to act on something, tick auto-create ticket and let assignment and SLA do the routing.
Where to go next
- Understand the whole module → How Device Monitoring Works
- Next in this module → Read the Network Map
- Check SSL Certificate Status
- View Patch Status
- See where this fits in the bigger picture → How a Device Problem Becomes a Fix
Was this article helpful?