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 Manager i10.62

Administer > Event Processing > Event Forwarding

Event Forwarding

The Event Forwarding manager enables you to set up rules to select and forward events to external event managers such as another OMi instance, an OM management server, or a Help desk application. These external managers are also referred to as event forwarding targets.

Event forwarding rules are used in conjunction with server connections to redirect selected events to specific event managers. Events can be forwarded for information or as a result of an escalation where the ownership of the problem is transferred to a more specialized group of experts.

Learn more

Tasks

How to create an event forwarding rule

In the Event Forwarding Rules pane, click the New Item button to open the Create New Event Forwarding Rules dialog box.
Enter a display name, and (optional) a description of the event forwarding rule being specified.
Select Active, if you want to make the event forwarding rule active immediately.
Select an event filter for the event forwarding rule from the Events Filter list. The filter determines which events to consider for forwarding.

Filters for Event Forwarding Rules can include filtering on the following date-related event attributes which, for example, help you to ignore outdated events:
- Time Created
- Time Received
- Time Lifecycle State Changed
Note The filters are only evaluated when the event is created and when the event is changed. If you create a filter that should trigger if the event is not closed within 12 hours and the event is not changed after 12 hours the forwarding rule will not trigger until something in the event is changed.

Tip To prevent events older than 6 hours from being forwarded to an Incident Management system, add the following AND clause to your forwarding filter:

AND Time Created is not older than 6 hours

Using Time Received would not solve the issue because the events were recently received by Operations Management, but the Time Created value is the time stamp from when the event was originally created. Old events are usually not relevant enough to be forwarded to the target trouble ticket system. They are suppressed from forwarding by adding the above clause, resulting in only the relevant events being placed in the queue to be forward to the Incident Management system.

If no appropriate filter is already configured, click the Browse (...) button, which opens the Select an Event Filter dialog box. Create a filter or edit an existing one. For information about filters, see Event Filters.
Select one or more target servers to which the events selected by this rule should be forwarded. For each target server, add it to the rule using the New Item button.

Note Events forwarded to OMi and identified as a duplicate are closed on all other connected servers where the event is stored. In addition, an annotation is added containing the event ID of the event which is the event that subsequent events become duplicates of.

If no target servers are configured, configure the required target servers first. For details, see How to create a connection to an OM server.

Note An actual connected server configuration cannot be exported, as these configurations are installation-specific. Importing an event forwarding rule creates a virtual server for each specified target server. These virtual servers must be associated with physical connected servers to enable the rule.
For each target server that you added to the event forwarding rule, specify a forwarding type.

The options include:
- Notify — Target server receives original events but no further updates
- Notify and Update — Target server receives original events and all further updates
- Synchronize — Target server receives original events and all further updates and sends back all updates
- Synchronize and Transfer Control — Target server receives original events and updates and sends back all updates. Ownership of the event is transferred to the other server. Only OMi users with special permission are allowed to close the event after control is transferred, for example, an Administrator.
  
  This option is available only if Enable synchronize and transfer control is enabled on the selected connected server. An operator may manually transfer control via the context menu of the Event Browser.
Note An automatic forwarding rule that is configured to transfer control of an event to a Connected Server may fail if the event has already been transferred to another server. In this case the following is done:
- The event is forwarded to the specified connected server as Notify and Update and not as Synchronize and Transfer Control.
- A log file entry is made to the log/opr-backend/opr-backend.log file.
- An annotation is made to the event with the log message. The author of the annotation is System:Forwarding.

Troubleshooting and Limitations

Send Help Center feedback