Set up threshold-based alarms for any plugin running on your monitored servers or devices, so Cloudmon notifies your team or triggers automated remediation the moment a plugin metric or status breaches its defined limit.
Plugins in Cloudmon are script-based and can collect metrics from any custom application, service, or hardware that standard monitoring methods do not cover. Because each plugin collects its own unique set of metrics, alarm rules are configured per plugin and are tied directly to the metrics that plugin reports. Cloudmon reduces alarm noise by requiring conditions to persist across consecutive intervals before firing, preventing momentary spikes from generating unnecessary alerts.
There are two ways to configure alarm rules for plugins:
Each alarm is built around a simple IF/THEN model, where you select a plugin metric, set a threshold, and define what happens when it is breached. Learn more.
Because plugins are script-based and custom to each deployment, the metrics available for alarming depend entirely on what each plugin collects. Below are example alarm configurations across the types of plugins commonly used in Cloudmon deployments:
| Use Case | Plugin Type | Metric | Suggested Threshold | Why |
| Plugin stopped reporting | All plugins | Plugin Status | Inactive for 1 interval | Catches silent script failures before they create undetected gaps in monitoring data. Configured by default on every plugin. |
| Database connection pool exhausted | MongoDB / database plugins | Active Connections | Above 90% of max connections for 2 intervals | Prevents application failures caused by new connections being rejected when the database connection pool is full. |
| Web server request failures spiking | Nginx / web server plugins | Failed Requests | Above 5% error rate for 2 intervals | Surfaces backend errors or misconfigurations that are degrading the end-user experience before they escalate. |
| GPU overheating under workload | GPU monitoring plugins | GPU Temperature | Above 85°C for 1 interval | Flags thermal issues early to prevent hardware damage or automatic GPU throttling under sustained load. |
| IoT device offline or unresponsive | IoT monitoring plugins | Device Availability | Below 100% for 1 interval | Immediately surfaces IoT devices that have dropped off the network, which may otherwise go unnoticed without dedicated monitoring. |
| Digital experience score dropping | Digital experience plugins | Experience Score | Below acceptable baseline for 3 intervals | Proactively identifies degraded user experience at a branch or location before end users raise complaints. |
Once saved, all triggers for a plugin are listed in the Triggers table under the Alarm Rule section within that plugin's Settings. Each row shows the trigger title, alarm severity, whether notifications are configured, whether a third-party service is linked, and whether a script is set to run. Triggers can be edited or deleted at any time using the action icons on the right.
To apply consistent alarm coverage across multiple plugins of the same type without configuring each one individually, save the rule as a reusable template under Settings → Configurations → Alarm Rules and associate it to a group.