Table Of Contents

Monitoring System Health with Alarms

Last Modified: March 31, 2021

Set rules that trigger alarm instances when a tag value meets certain conditions.

Before setting up an alarm, ensure you have created a tag for the value you want to monitor.
  1. Under Utilities»Tags, double-click the tag for which you want to create an alarm rule.
  2. Under Alarm Rules, click Create.
  3. Specify a name for the rule.
  4. Specify one or more tag paths to search for.
    • To apply the alarm rule to one tag, specify the absolute path of the tag.
    • To apply the alarm rule to multiple tags of the same data type, use the wildcard character (*) to represent any number of characters in the path.
    The table below illustrates examples of each type of tag search path.
    Example Tag Search Path Result
    system1.Health.Disk.Total Searches for one tag, system1.Health.Disk.Total.
    *.Health.Disk.Total Searches for all tags ending with .Health.Disk.Total.
  5. Choose the workspace you want the rule to belong to. The workspace you choose determines which data the rule processes. For more information about workspaces, refer to the access control help.
  6. Choose whether the alarm rule evaluates tags based on their assigned value or their last updated time.
  7. Specify the data type of the tags for which you are creating an alarm rule. The data type you specify must match the data type specified in the tag.
  8. Specify a name and description to appear each time the alarm instance becomes active.
  9. Configure conditions to specify when this rule creates an alarm.
    1. Under Conditions, click Create.
    2. Choose the Severity Level you want to define conditions for.
    3. Choose the Comparator you want the alarm rule to use to process values.
    4. Specify a Set Point or Compare To value for the tag this alarm rule monitors. If you're monitoring timestamp values, you can choose to compare values to a specific date and time or to the current time.
    5. Specify a Deadband for the alarm. The deadband determines how far the tag value must be from the set point to clear an active alarm. Use the following table to determine how deadband values operate in each comparison scenario.
      Comparator Value needed to clear the alarm
      Less Than Any value greater than or equal to [Set Point]+[Deadband]
      Less Than or Equal Any value greater than [Set Point]+[Deadband]
      Greater Than Any value less than or equal to [Set Point]-[Deadband]
      Greater Than or Equal Any value less than [Set Point]-[Deadband]
      In Range Any value less than [Set Point (Low)]-[Deadband] or greater than [Set Point (High)]+[Deadband]
      Equal Any value equal to [Set Point]+[Deadband]
      Not Equal Any value not equal to [Set Point]+[Deadband]
    6. If this alarm rule compares timestamp values to the current time, specify an Offset. The offset determines how close to the current time a timestamp must be to trigger an alarm. If a timestamp leaves the offset range, the alarm clears.
    7. Choose a notification strategy to alert users about alarm activity. Users specified in the strategy receive notifications whenever the alarm reaches a new maximum severity. For example, users receive a notification if a change in tag values causes a moderate-severity alarm instance to become high severity.
    8. Click Create.
  10. Click Create at the top of the page.
  11. When an alarm rule triggers an alarm, you can clear the alarm, acknowledge it, or do neither. The following table illustrates the alarm states that result from different actions you perform on an active alarm.
    Clear? Acknowledged? Resulting alarm state
    Yes, due to change in tag value Yes Alarm becomes inactive.
    Yes, due to change in tag value No Alarm stays active.
    Yes, due to user force clearing the alarm instance Yes (force clearing acknowledges the alarm) Alarm becomes inactive.
    No Yes Alarm becomes acknowledged but stays active.
    No No Alarm stays active.

Recently Viewed Topics