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

Get started > Use Cases > How to Perform Daily Monitoring?

How to Perform Daily Monitoring?

This end-to-end use case describes how to perform the daily monitoring process.

Task 1. Check the UCMDB UI

Check the following items:

The status of each probe:
- The status should be Connected.
- The last access time should be within 30 seconds.
- The probe version should be up to date.
The status of the jobs on each probe:
- The status of each probe should be Connected.
- The running job number and thread number should be as expected and will not cause performance issue. For more information, contact Support.
- Sending queue should not be accumulating.
The total CI number:
- The total CI number should not exceed the limitation.
- The CallhomeEvent CI number should not be accumulating.
- The total Computer CI number should be as expected.

Check the following items:

Regular CPU and memory usage of the UCMDB server.
Regular CPU, memory, and Disk I/O usage of the server database.
Confirm no Java dump file exists in the following folder:

<UCMDBServer_Installation_Folder>\bin

Check the following items:

Regular CPU and memory usage of the probe service.
Regular CPU and memory usage of the ProbeDB service.
Regular CPU and memory usage of the XMLEnricher service.
The probe server has enough disk space.
Confirm no Java dump file exists in the following folder:

<DataFlowProbe_Installation_Folder>\bin
Check scan files if the Inventory Discovery by Scanner job is running:
- All the files in the following folder should be updated within one hour:
  
  <DataFlowProbe_Installation_Folder>\runtime\xmlenricher\Scans\incoming
- All the files in the following folder should be updated within eight hours:
  
  <DataFlowProbe_Installation_Folder>\runtime\xmlenricher\Scans\sending
  
  A few files that were updated eight hours ago might be cause by system glitch and should be deleted.
- The Corrupt, Delta, or Error subfolder of the following folder should not contain any files:
  
  <DataFlowProbe_Installation_Folder>\runtime\xmlenricher\Scans\failed
  
  Such a file can be caused by exception in the xml enricher. Try to reprocess the scan file by copying it to the incoming folder.