Skip to content


A rule combines one or more triggers with one or more destinations and a customized message. When conditions match any trigger in a rule, Zenoss Cloud sends a message to all the destinations in the rule.

Only rules can initiate actions. Your user account must have the Manager role to create and manage rules in the Zenoss Cloud interface.

You can configure a rule to repeat its action each time one or more of its tigger queries is satisfied.


Create triggers and destinations before creating a rule. To accelerate the process of creating a rule, you can use the Create Action Rule button on an events console.

Adding a rule

You can add a rule through the Zenoss Cloud interface on the RULES tab of the ADMIN > Actions page. You can also use the Zenoss API to create a rule.

When you add a rule with the ADD RULE dialog, you specify the rule with the fields in the following table.

Field Description
Enable A toggle that determines whether the rule is active or inactive. The default is active.
Rule name

A unique, short identifier for the rule (required).

The name of a rule cannot be changed after the ADD RULE dialog is saved.

Description Additional text to further describe the rule.
Repeat notification

A toggle that determines whether to repeat the action (send notifications) for each matching trigger. The default is not to repeat notifications. When this option is enabled, the dialog expands so you can specify the repeat interval:

  • Repeat interval—The integer of the repeat interval.
  • Interval type—The unit of time of the repeat interval.

Send updates

A toggle that determines whether to p erform the action (send notifications) if the same trigger condition occurs, but has been updated in a significant way. For example, an event being closed, acknowledged, or changing severity. The default is not to send updates.

Triggers A list of triggers to associate with the rule.
Destinations A list of destinations to associate with the rule.

The text to send to destinations. You can include one or more templates in the text.

Slack and Webhook destinations receive the customized message defined in a rule, while email destinations receive the message defined in the Subject and Message body fields of a destination.

Tags A list of arbitrary terms to associate with the rule.