Specifying Predicates and Values in Subscriptions

The following sections explain how xMatters evaluates predicates and predicate/value pairs when determining recipients for a Subscription notification.

Specifying values for list-type predicates

When selecting values for a list predicate, you can select a single value, multiple values, “ANY” values, or leave the field blank. xMatters considers it a match if any one selected value matches the predicate values in the Event. If you select ANY, xMatters will consider any value for the predicate a match for the Subscription, including values not specified in the Subscription Domain.

For example, assume that a Subscription Domain includes a list predicate of “Service”, with pre-defined values of “A”, “B”, and “C”. The following table summarizes the match results of different predicate values within an incoming Event, including a value not specified within the Subscription Domain:

Predicate in Event

Subscription Criteria

Match

A

ANY

Yes

A

A, B, C

Yes

A

A, ANY (stored as ANY)

Yes

A

NULL (not specified)

Yes

A

B

No

Z

ANY

Yes

Z

A, B, C

No

Z

A, ANY

Yes

Z

NULL

Yes

Z

B

No

Subscribing to predicates with multiple values

You can enable the integration agent to submit predicates with multiple values, and create Subscriptions for those predicates. (For more information about enabling this feature, see the xMatters Integration Agent Guide.) When dealing with these predicates, xMatters considers it a match if any subscribed value appears in the predicate.

For example, assume that an incoming Event has a predicate with multiple values. The following table summarizes the match results of different Subscriptions for that predicate:

Determining Subscription Results for Predicates with Multiple Values

Predicate Values

Subscription Criteria

Match

A, B, C

A

Yes

A, B, C

A, C

Yes

A, B, C

A, Z

Yes

A, B

B, C, Z

Yes

A, B, C,

Z

No

Subscribing to multiple predicates

The relationship between predicates in a Subscription is considered an “AND”. For the subscription to match, the conditions must match for each predicate.

For example, assume that a Subscription Domain is created with two predicates, “Service” and “Severity”, and a Subscription is created against Service values of A or B, and Severity of ANY:

Subscriptions and missing predicates

It is possible that a submitted Event will not contain the predicate needed for the Subscription Domain. If the event predicate is missing it will be considered a match for all Subscriptions that have subscribed to the value of “ANY”, and any Subscriptions that have a null value. A literal value does not result in a match.

The following table describes the results of different Subscription criteria based on the value of the predicate contained in the Event:

Determining Subscription Results for Missing or Unspecified Predicates

Predicate in Event

Subscription Criteria

Match

Unspecified

Non-empty

No

Unspecified

Empty

Yes

Unspecified

ANY

Yes

Specified, but empty

Non-empty

No

Specified, but empty

Empty

Yes

Specified, but empty

ANY

Yes

Specified

Non-empty, including specified value

Yes

Specified

Non-empty, not including specified value

No

Specified

Empty

Yes

Specified

ANY

Yes