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

Use > Monitor health > Event Type Indicators

Event Type Indicators

Event type indicators (ETIs) are attributes of OMi events used to categorize events according to the type of occurrence in the managed IT environment.
To set event type attributes, you can specify the ETI Hint value in the OMi Monitoring Automation policies. In OM, you can alternatively configure events to include the custom attribute ETIHint to set event type attributes. If the custom attribute is not configured, event type attributes can be set by indicator mapping rules. If adequate information is not available, no ETI is set.

After defining appropriate topology-based event correlation (TBEC) rules, events are correlated based on the ETIs. The correlation rules relate types of events that can occur on the CI, or on a related CI.

Learn More

ETI Characteristics

ETIs are characterized by the following:

Categorize type of event to abstract multiple event sources.
ETIs consist of at least one value. This value is used to describe the event occurrence in the environment, for example, an ETI could read: System restart:Occurred. Usually, you do not need to set any values for such ETIs because, as a convenience, one value is created that is called Occurred.
ETIs are structured according to a name:state:value format. For example, an indicator could be: CPULoad:Bottlenecked:100, with CPULoad being the name, Bottlenecked being the state, and 100 being the value. The state Bottlenecked is mapped to a severity, for example Critical.
Note that, as explained in the example above, some ETIs only consist of the name and state, without a value.
Events contain an ETI attribute. ETIs do not exist as instances in their own right. An ETI Hint in an event is resolved to an ETI if the ETI has been defined in OMi for a CI type and the event has a related CI of the same CI type (or a child CI type) as defined for the ETI.
ETIs without a corresponding HI are not shown within the Health Indicators pane.
No manual reset necessary. An ETI is just an event attribute.

A configuration item inherits ETI assignments, including HIs, from its parent configuration item type. For example, ETIs assigned to the configuration item type Database also apply to the configuration item type Oracle and are applied to any Oracle Database configuration items.

Tasks

Send Help Center feedback