Alarm filtering (TRIPWIRE v4.5)
posted 2018.03.04 by Clark Wilkins, Simplexable

We've just released an important change in alarms management in v4.5 that bears some explanation. A core concept in the design of Tripwire 4 was the abillity to set an alarm for all eligible sites at once. For example, you might want an alert that triggers when the helium level goes below 60%. When you set this as a general alarm, the system finds all of your active sites that monitor helium levels and sets the alarm for each one.

That's convenient but there are cases where you need something more specific. For example, if you add a new site, you don't want to set a new alarm for every site, but you do want to set some parameters for this site. Another example is that you might want to set an 80% threshold for magnets of one type, and a 50% threshold for magnets of another. If you're only allowed global alerts, you have to set the alert for both types on all magnets, and then remove the ones you don't really want one at a time.

For example, we're going to go into a specific group of sites and set a 70% helium alert specific to these sites.

The filter is now set to this subset (site group) instead of all sites (the default).

You can see in the following screenshot, some TRIPWIRE units (part of the group) have the alarm set, but others don't.

To summarize, you have three choices of scope when setting alerts:

  • All active/relevant sites (default).
  • All active/relevant sites in a specific site group (shown above).
  • A specific active site.

As always, you can modify or remove any alert as desired.