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 > Structured Log File Policies > How to Collect Event Data from Structured Log Files

How to Collect Event Data from Structured Log Files

This task describes how to collect event data from structured log files.

Prerequisite: Make sure the following applies:
1. Your Operations Connector is configured to work with OMi by using the bsmc-conf tool.
2. The certificate request is approved on the OMi side.
3. Your Operations Connector is set up as a connected server in OMi.
In the Operations Connector user interface, click in the toolbar. Then click Event > Structured Log File.

Alternatively, double-click an existing policy to edit it.
In the Properties page, define information that is related to the policy itself (for example, the name and description of the policy).
In the Source page, define the structure pattern of the log file by using the OM pattern-matching language.
In the Mappings page, map the structured log file's input data properties to custom variables.
Optional. In the Defaults page, configure the default settings for all events generated by the policy (for example, default event correlation settings).
In the Rules page, define what the policy should do in response to a specific type of event.
In the Options page, configure several policy behaviors (for example, pattern matching options).
Click Save and Close to save the policy and close the editor.
Optional. If the list of policies does not refresh automatically in the Operations Connector user interface, click in the toolbar.

Related topics