Filter clauses for an IBM Netcool Operations Insight ObjectServer integration

For an integration between IBM Concert Operate and IBM Tivoli Netcool/OMNIbus, you can use the filter clause to define the alerts that you want to send to IBM Concert Operate. You can create filter clauses that are suitable for your environment by using an ObjectServer SQL where clause syntax.

To generate filter clauses, use fields from the ObjectServer alerts.status table, such as ServerName, Agent, or Manager for the syntax. The following example shows this syntax:

ServerName IN ('Server1','Server2')

Filter clause examples

The following table outlines some of the examples of FILTER clause and their description:

Filter examples	Description
`Agent != 'OMNIbus SelfMonitoring'`	This filter clause filters all events in the ObjectServer `alerts.status` table with the `Agent` field not equal to `OMNIbus SelfMonitoring`.
`Manager not like 'OMNIbus Self Monitoring*'`	This filter clause filters all events in the ObjectServer `alerts.status` table with the `Manager` field not starting with `OMNIbus Self Monitoring`.
`Severity >= 2`	This filter clause filters all events in the ObjectServer `alerts.status` table with `Severity` field equal to or beyond the warning level. Thus, the integration selects only those alerts that have severity more than or equal to 2. For more information about severity level representation, see Event severity levels.
`ServerName IN ('AGG_P','AGG_B')`	This filter clause filters all events in the ObjectServer `alerts.status` table with ServerName equal to `AGG_P` and `AGG_B`. Thus, the integration selects only those alerts that originate from `'AGG_P'` and `'AGG_B'`.

The following are some examples of the Manager field:

OMNIbus Self Monitoring @AGG_P
OMNIbus Self Monitoring @AGG_B

Where AGG_P and AGG_B are server names.

You can use Boolean operators such as AND, OR to join conditions in the filter clause syntax. For example,

Acknowledged>0 AND ServerName IN ('NCOMS_US','NCOMS_CA')