Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Connector10.11

Administer > Policies > XML File Policies > XML File Policy User Interface > Configuring Options in XML File Policies

Configuring Options in XML File Policies

The options tab enables you to configure several policy behaviors, for example which events or metrics are logged locally, how the policy handles unmatched events, and defaults for pattern matching in policy rules.

To access

In the Operations Connector user interface, click in the toolbar. Then click Event > XML File.
In the Operations Connector user interface, click in the toolbar. Then click Metric > XML File.

Alternatively, double-click an existing policy to edit it.

Tasks

How to configure options for XML policies

In the Options page, configure which events or metric records are logged locally, how the policy handles unmatched events or metric records, and defaults for pattern matching in policy rules.

Related tasks

How to Collect Event Data from XML Files

UI Descriptions

Options Page

UI Element

Description

Log Local Events

Defines which incoming events are logged. These events are logged on the Operations Connector host system in the log file:

Windows: %OvDataDir%\log\OpC\opcmsglg

Linux: /var/opt/OV/log/OpC/opcmsglg

that match a rule and trigger an event Logs any events in the event source that match the policy rules.

that match a rule and are ignored Logs any events in the event source that are suppressed. (Suppressed events are not sent to OMi.)

that do not match any rule Logs any events that do not match any of the rules in the policy.

Unmatched Events

Send an event to OMi when the input event does not match any rule in the policy because none of the conditions apply or because the policy does not contain any rules. This ensures that unexpected events that might be important do not go unreported. By default, unmatched events are ignored.

Each policy that sends unmatched events to OMi creates an event with the default values of the policy.

If you want a policy to send events only with the default values, omit all rules from the policy.

The agent creates an event for an unmatched event only if the input event is unmatched in all policies on the Operations Connector system. The agent sends only one event for each unmatched input event.

If several event policies forward unmatched events to OMi, you could receive multiple events about a single input event.

are forwarded to OMi Server Sends unmatched events to OMi.

are forwarded to OMi Server with state 'closed' Sets the unmatched event's lifecycle status to Closed before sending it to OMi.

are ignored Ignores unmatched events.

Log incoming Metric data

Defines which incoming metric records are logged. These records are logged on the Operations Connector host system in the log file:

Windows: %OvDataDir%\log\OpC\opcmsglg

Linux: /var/opt/OV/log/OpC/opcmsglg

that match a rule and are stored Logs any metric records in the metric source that match the policy rules.

that match a rule and are ignored Logs any metric records in the metric source that are suppressed. (Suppressed metric records are not sent to OMi.)

that do not match a rule and are ignored Logs any metric records that do not match any of the rules in the policy.

Unmatched Records

Store records that do not match any rule Operations Connector stores events and metrics that do not match any rule and sends them to OMi.

Pattern Matching Options

Defines case sensitivity and field separators for all rules.

Case sensitive check Defines whether the case (uppercase or lowercase) of a text string is considered when the pattern of a rule is compared with the source data. When switched on, a match only occurs if the use of uppercase and lowercase letters is exactly the same in both the source data and the pattern. This is the default setting.

Field Separators

Defines which characters should be considered to be field separators. Field separators are used in the pattern as separator characters for the rule condition. You can define up to seven separators, including these special characters:

\n New line (NL)
\t Horizontal tab (HT)
\v Vertical tab (VT)
\b Backspace (BS)

\r Carriage return (CR)
\f Form feed (FF)
\a Alert (BEL)
\\ Backslash (\)

For example, if you wanted a backslash, an asterisk, and the letter A to define the fields in the event, you would type \\*A (with no spaces separating the characters).

If you leave this box empty, the default separators (a blank and the tab character) are used by default.

You can set case sensitivity and separator characters for individual rules in a policy by clicking the button in rule's match condition.

Apply to All

Applies the pattern matching options to all existing rules in a policy. This overwrites any modifications made to the pattern matching options in individual rules.

If you change the pattern matching options and do not click Apply to all, they only apply to all new rules in a policy.

Send Help Center feedback