Skip to content

Adding stale data triggers

In Actions, you can create a stale data trigger to notify you when Zenoss hasn't received a metric or event after a specified duration of time. This feature is useful when you have important metrics or events that you expect to regularly receive, so failing to receive them would indicate a problem that requires your attention.

Stale data is data that is outdated or obsolete, and is no longer accurate or needed for your daily operations. You have essentially stopped receiving information for a metric or event and need to restore dataflow. Creating a trigger notifies you when your specified metric or event contains stale data so you can resolve the issue.

Keep in mind that if a trigger matches more than one event or metric, it will send one notification per each event or metric that matches the trigger. For example, you might have hundreds of entities sending the "CPU-Utilization" metric regularly. If you had a trigger that just matched that metric name with no additional query criteria, and Zenoss stopped receiving the metric from five of those entities, you would receive five notifications.

Setting up stale data triggers

To set up a stale data trigger, first determine the destination and then create the trigger. Then link both the trigger and the destination to a rule. When conditions match your stale data trigger in the rule, the action service sends a message to the destination specified in the rule. In this case, you might set up the trigger and the rule such that if Zenoss is no longer receiving data for the metric or event after a certain duration, your destination is notified.

A stale data notification is considered clear when Zenoss receives new data for the event or metric identified in the notification. When adding your rule, be sure to turn on the Send updates option in the ADD RULE dialog box so you can receive a clear notification for these cases. If you want to continue receiving notifications about stale metrics and events while they remain stale, turn on the Repeat notifcation option for the rule.

Add a stale data trigger

The following steps guide you through adding details for the stale data trigger, specifying trigger criteria, and setting a time duration. The trigger is sent when one unique event or metric is met in the criteria.

Note

You must be assigned the Manager role to create a trigger.

Perform the following steps:

  1. Open the ADMIN > Actions page, and then click the TRIGGERS tab.

  2. In the upper-right corner, click ADD TRIGGER.

  3. The ADD TRIGGER dialog box opens.

    In the Trigger details section, enter the following information:

    Field Description
    Trigger name

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

    The name can't be changed after you select SAVE.
    Description (Optional) Enter text to describe the trigger.
    Type

    In the dropdown list, select the Stale Data option. You can see that the dialog box now displays additional criteria fields.
    Tags (Optional) Add one or more terms to associate with the trigger.

  4. In the Trigger criteria section, create a query to identify specific stale data. Enter the following information:

    Field Description
    Data type

    Enter the type of data to include in the query. You can select Event or Metric. This is a required field.

    • If you select Metric, you must enter the name of the metric. Click in the Metric name field and enter the first few letters of a metric name. Zenoss Cloud displays a list of names to choose from. For assistance finding a metric name, go to ADMIN > Dictionary, then select the METRICS tab.
    • If you select Event, you must enter a query in the Query field.
    Query Create a query to identify one or more entities that collect the metric. For more information, see Trigger queries and Metric trigger fields.
    Duration

    Enter the length of time in seconds for meeting the conditions of the trigger. For example, to set a duration of one hour, enter '3600'. This is a required field

    The minimum value is 600 seconds, or 10 minutes. The maximum value is 86400 seconds, or 24 hours.

    For more information, see Trigger queries and Event trigger fields.

    Best Practice

    As a best practice, use Entity: Production State equal to Production as a trigger criteria. This criteria can prevent matches that are "false positives" against non-production entities.

    For example, include this criteria to avoid matching against devices that might be in Maintenance.

    To match on additional production states, consider using the greater than or greater than or equal to operators.

  5. Click SAVE.