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 > Sizing > Universal Discovery Capacity > Planning Your Discovery Schedule

Planning Your Discovery Schedule

Go to Discovery Use Cases and identify the list of discovery jobs you want to run to meet your operational needs.

Let us assume two basic use cases:

Agentless discovery
Agent-based discovery (two options, with or without call home setting)


Agentless Basic Discovery	Agent-based discovery
Agentless Basic Discovery	Option 1: For client devices with call home setting	Option 2: For datacenter devices without call home setting
ICMP Ping	Call home processing	ICMP Ping
Host Connection by Shell	Inventory discovery by scanner	Host Connection by Shell
Host Resources by Shell		Inventory discovery by scanner
Host Applications by Shell

When you think about these basic use cases, a couple of questions will arise:

How many probes are required to complete your discovery?
How frequently can you run these jobs? What is the valid business use case on the rediscovery interval?
Is there an upper limit on the number of trigger CIs a probe can handle?

Planning your discovery capacity based on your use cases will give you good handle on the number of related CIs per discovered node. When planning capacity, among other issues, you should consider the ratio of managed nodes in your CMDB to node-related CIs. Node-related CIs include all CIs of types that are subclasses of Application Resource, Node Element, or Running Software.

The following diagram gives you an idea on the number of node-related CIs you can discover for each managed node based on the size and use cases. This number depends on the size of your deployment and the number of managed nodes the more managed nodes you maintain in the CMDB, the fewer node-related CIs you can discover for each managed node.

Managed Nodes to Node-Related CIs Ratio

For example, in an enterprise deployment, if you are running 336,000 managed nodes, you can discover 160 node-related CIs for each managed node. If you are running only 108,000 managed nodes, you can discover 500 resource CIs for each managed node. This ratio will give you an idea on the scalability and deployment strategy.

Send Help Center feedback