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)`

Universal CMDB11.0

Use > Data Flow Management > Adapter Management > Adapter Configuration > How to Configure Global Probe Result Filtering > Configure Filtering Using the globalFiltering.xml File

Configure Filtering Using the globalFiltering.xml File

This document explains how to perform filtering using a manual method. If you want a UI-driven solution to performing this task, see Configure Filtering in UCMDB.

Note

You can use regular expressions in filters.
Attributes in the filter should be of type string only. For details on CI attribute types, see Attributes Page.
You can use the "between" operator when filtering results, but only when the Object class is “ip_address” and the attribute name is “name”.
A result is considered to be a match only if all filter attributes have the same values as those in the CI. (If one of a CI's attributes is not specified in the filter, all the results for this attribute match the filter.)
A CI can match more than one filter. The CI is removed or remains according to the filter in which it is included.
Recursive Filtering. Using global filtering, you can filter out a CI so that it is not included in the filter results. This CI may be a root CI, containing other CIs or relationships. By default, during the filter process, the contained CIs and relationships, as well as any CIs related to them, are added to the filter results—including the root CI. This causes undesired filter results. Recursive filtering corrects this by ensuring that if a root CI is filtered out, then any contained CIs or relationships are filtered out too, such that the root CI cannot be found again.

To enable recursive filtering:

In the globalFiltering.xml file, under the resultFilters element, locate the recursiveFilter attribute. (If the recursiveFilter attribute does not appear, then you must add it.) Set the attribute value to true.

Note: By default, recursive filtering is disabled, that is recursiveFilter = false.
DFM filters first according to the <includeFilter> and then applies the <excludeFilter> on the results of <includeFilter>.

Configure a Filter

Open the globalFiltering.xml file. (Adapter Management module > Resources pane > Packages > DDM Infra > Configuration Files)

The code in displayed in the View pane:

<resultFilters>
    <excludeFilter>
        <vector />
    </excludeFilter>
    <includeFilter>
        <vector />
    </includeFilter>
</resultFilters>

<excludeFilter>. When a vector marker is added to this filter, all CIs that match the filter are removed. If this marker is left empty, all results are sent to the server.
<includeFilter>. When a vector marker is added to this filter, all CIs that do not match the filter are removed. If this marker is left empty, all results are sent to the server.

The following example shows an IpAddress CI that has address and domain attributes:

<vector>
    <object class="ip_address">
        <attribute name="name" type="String">192\.168\.82\.17.*</attribute>
        <attribute name="routing_domain" type="String">DefaultProbe</attribute>
    </object>
</vector>

If this vector is defined in <includeFilter>, all results not matching the filter are removed. The results sent to the server are those where the ip_address matches the regular expression 192\.168\.82\.17.* and the ip_domain is DefaultProbe.

If this vector is defined in <excludeFilter>, all results matching the filter are removed. The results sent to the server are those where the ip_address does not match the regular expression 192\.168\.82\.17.* and the ip_domain is notDefaultProbe.

The following example shows how logical OR and logical AND statements can be created.

Example of 'OR' condition:

<vector> 
    <object class="ip_address">
        <attribute name="name" type="String">192\.168\.82\.17.*</attribute>
    </object>
    <object class="ip_address">
        <attribute name="name" type="String">192\.168\.82\.18.*</attribute>
    </object>
    <object class="ip_address">
        <attribute name="routing_domain" type="String">DefaultProbe</attribute>
    </object>
</vector>

If this vector is defined, all results where the IP address matches "192\.168\.82\.17.* " OR matches "192\.168\.82\.18.* " OR routing_domain is "DefaultProbe" is filtered.

Example of 'AND' condition:

<vector>
    <object class="ip_address">
        <attribute name="name" type="String">192\.168\.82\.17.*</attribute>
        <attribute name="routing_domain" type="String">DefaultProbe</attribute>
    </object>
</vector>

If this vector is defined, all results where the IP address matches "192\.168\.82\.17.* " AND routing_domain is "DefaultProbe" is filtered.

The following example shows an ip_subnet CI that has no attributes.

<vector>
    <object class="ip_subnet">
    </object>
</vector>

Related Information

Send Help Center feedback