Ability to specify operation for multiple resource filters

Description

Right now, if one resource filter is matched, then the threshold is evaluated. It would be nice to be able to configure whether one or all filters have to match.

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed May 20, 2010 at 11:10 AM

from the commit log:

The file thresholding-config.xsd was modified to include a new
attribute on basethresholddef called "filterOperator". This attribute
has two possible values: "or", "and". The attribute is optional, and if
it's not supplied, the default value will be "or" (because this is the
current default behavior for resource-filter evaluation).

If you specify filterOperator with the word "and" as a value, then ALL
resource filters should match in order to trigger the threshold. For
example:

<threshold type="high" ds-name="ifInOctets" ds-type="if" value="90"
rearm="50" trigger="1" filterOperator="and">
<resource-filter field='snmpifdescr'>wlan0</resource-filter>
<resource-filter field='snmpifspeed'>100000000</resource-filter>
</threshold>

Alejandro Galue March 15, 2010 at 2:03 PM

Fixed on 1.6 branch (rr9228ea8fbd01)

Alejandro Galue March 15, 2010 at 1:16 PM

Fixed on master branch (rb5b3695edefc) for OpenNMS 1.7.x series.

Still need to work on branch 1.6.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created November 9, 2009 at 8:07 AM
Updated January 27, 2017 at 4:26 PM
Resolved November 5, 2010 at 4:46 PM