Working with triggers

Defining a trigger involves the following steps:

1. Create the trigger. This step defines the name of a trigger.
2. Edit the trigger. This step defines the rules of the trigger and optionally, the users who can edit the trigger.

All new triggers include the following rules:

• The device production state equals Production.
• The event severity is greater than or equal to Error.

Most event properties can be used in rules, including:

• Device and device component
• Event summary
• Event count
• Device location

For more information about event properties, see Event fields.

Rules can use the following operators for comparisons:

• Equals / Does not equal
• Contains / Does not contain
• Greater than / Greater than or equal to
• Less than / Less than or equal to

Text comparisons are case-sensitive.

Best practice recommendations

Create triggers that match their target events with the simplest possible set of rules. Even so, the simplest possible set of rules may be complex.

To further refine trigger and notification processing, use event mappings to transform events. The event processing service performs transforms before examining triggers.

Typically, a trigger should include the following rules:

• The device production state equals Production.
• The event severity equals (some value).
• The event status equals New.

If a rule uses the Count property, choose one of the following comparisons instead of the equals comparison:

• Greater than / Greater than or equal to
• Less than / Less than or equal to

Otherwise, when a notification that uses the trigger includes a delay, an equals comparison may never match, because the count could change before the delay expires.

By default, Resource Manager supports 200 triggers without performance implications. If you have more than 200 triggers, please contact Zenoss Support.

For more information about triggers, take a look at this video.

Creating a trigger

Follow these steps:

1. Navigate to EVENTS > TRIGGERS.

   

2. Click the Add icon.

   

3. In the Id field, enter a name for the trigger.

   Use descriptive names. For example, LinuxDBServerFileSystemHigh.

   Only uppercase and lowercase letters, digits, spaces, and underscores are allowed in trigger names.

4. Click Submit.

Editing a trigger

Follow these steps:

1. Navigate to EVENTS > TRIGGERS.

2. Double-click the name of the trigger to edit.

   

3. Modify the default rules, add new rules, or add subordinate rules.

   To identify the properties to include in a rule, navigate to EVENTS > EVENT CONSOLE and review examples of the type of event for which the trigger is targeted.

4. Click Submit.