Automatically apply alert profiles, user groups, third-party integrations, groups, and tags to monitors that match defined conditions, keeping configuration consistent across your environment without manual updates.
Configuration Rules let you define conditions that match a set of monitors, then automatically apply a consistent set of actions to every monitor that matches, such as assigning an alert profile, notifying specific user groups, or appending tags. This removes the need to manually update each monitor individually whenever a new device of a given type is added, or whenever your alerting or grouping conventions change.
Navigate to Settings → Configurations → Configuration Rules to manage rules. The page has two tabs: Configuration Rules, where rules are created and listed, and Execution History, where past rule runs are logged. The rules list shows each rule's name, description, monitoring type, who created and last updated it, and can be filtered by monitor type using the dropdown in the top right.
Navigate to Settings → Configurations → Configuration Rules and click Add. The Add Configuration Rule panel is organized into three sections: Basic Information, Filter Conditions, and Actions.
The Basic Information section sets the name, scope, and matching behaviour for the rule.
| Field | Description |
| Name* | A name for the rule. |
| Description | Optional notes describing what this rule does, to help other admins understand its purpose later. |
| Monitoring Type* | The type of monitor this rule applies to. Only monitors of this type are evaluated against the rule's Filter Conditions. |
| Stop executing other rules after this rule matches | When enabled, no further rules are evaluated for a monitor once this rule has matched it. Use this to establish a clear priority order when multiple rules could otherwise apply to the same monitor. |
The Filter Conditions section defines which monitors the rule applies to, based on criteria you specify.
Choose Match All (AND) if a monitor must satisfy every condition added to be matched, or Match Any (OR) if satisfying any single condition is enough. If no conditions are added, the rule matches every monitor of the selected Monitoring Type, as shown by the "No conditions added. All monitors will match." message. Add one or more conditions to narrow the scope to a specific subset of monitors, such as those carrying a particular tag or belonging to a particular group.
The Actions section defines what Cloudmon applies to every monitor that matches the rule's conditions.
| Field | Description |
| Alert Profile | The alert profile to apply to matched monitors. This replaces any alert profile already assigned to a matched monitor. |
| User Groups | The user groups to notify when alerts are triggered on matched monitors. |
| Third Party Integrations | Third-party integrations to use for alert notifications on matched monitors. |
| Groups | The group to assign to matched monitors. Click Append to add this group alongside any existing groups, or Replace to remove other groups from the monitor while the rule runs. |
| Tags | The tags to assign to matched monitors. Click Append to add these tags alongside any existing tags, or Replace to remove other tags from the monitor while the rule runs. |
Click Save. The rule is evaluated against monitors of the selected Monitoring Type and the configured actions are applied to every match.
Navigate to Settings → Configurations → Configuration Rules → Execution History to view a log of past rule runs. This is the first place to check when a rule does not appear to have applied its actions as expected, since it records when each rule last ran and what it matched.
When more than one Configuration Rule could apply to the same monitor, all matching rules run in turn and their actions are applied cumulatively, unless a rule has Stop executing other rules after this rule matches enabled. In that case, once that rule matches a monitor, no further rules are evaluated for it. Use this toggle on higher-priority rules to prevent broader, lower-priority rules from overriding their actions on the same monitor.
| Symptom | Likely Cause | Fix |
| A rule's actions were not applied to an expected monitor | The monitor's type does not match the rule's Monitoring Type, the Filter Conditions excluded it, or an earlier rule with "Stop executing other rules" enabled already matched it | Check Execution History to confirm whether the rule ran and what it matched. Review the Filter Conditions and check for an earlier rule with stop-on-match enabled |
| A monitor lost its existing groups or tags after a rule ran | The rule's Groups or Tags action was set to Replace rather than Append | Edit the rule and switch the affected action to Append if existing groups or tags should be preserved |
| A monitor's alert profile keeps reverting to one set by a rule | A Configuration Rule with that Alert Profile action is still matching the monitor and re-applies the profile each time it runs | Adjust the rule's Filter Conditions to exclude the monitor, or remove the Alert Profile action from the rule |
| Too many monitors matched a rule unintentionally | No Filter Conditions were added, so the rule matched every monitor of the selected Monitoring Type | Add Filter Conditions to scope the rule to a specific subset of monitors |