attributes-match (Event Policy)

Syntax

Hierarchy Level

Description

Execute an event policy only if the attributes of two events are correlated or if the attribute of one event matches a regular expression. By configuring an event policy to take an event's attributes into account in addition to the event itself, you can configure more precise event policy matching.

The events referenced in the attributes-match statements must be either the trigger event or the correlating events included in the event policy’s within statements. You must include one or more within statements in the same policy configuration if the attributes-match statement includes the equals or starts-with options, or if it includes a matches option that includes a clause for an event that is not specified at the [edit event-options policy policy-name events] hierarchy level.

An attributes-match statement can include multiple comparison statements. The system evaluates multiple comparison statements using a logical AND operator. Thus, to execute the event policy, all of the attributes-match conditions must evaluate to true.

You can include event policy variables within the statement to differentiate between a trigger event attribute and a correlated event attribute. You can use variables of the following forms:

• {$$.attribute-name}—The double dollar sign ($$) notation represents the event that is triggering a policy. When combined with an attribute name, the variable resolves to the value of the attribute associated with the triggering event.

• {$event.attribute-name}—The single dollar sign with the event name ($event) notation represents the most recent event that matches event. When combined with an attribute name, the variable resolves to the value of the attribute associated with that event.

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

maintenance—To view or add this statement in the configuration.

Release Information

Statement introduced in Junos OS Release 7.5.