Excluding classes and datasets for processing Dashboard parameters

You can configure classes and datasets that will be excluded while processing KPIs and Datasources utility.

Function	Parameter	Description
Exclude classes and datasets for Data sources processing	Exclude overlay dataset Processing	If set to True, does not process overlay dataset instances.
	Exclude Datasets	While processing data sources, specify the datasets to be excluded from datasources utility processing.
	Exclude Classes	Specify the classes in a datasource to be excluded for processing.
Exclude classes for KPI processing	Completeness: Exclude Classes	Specify the classes to be excluded while processing instances for completeness.
	Duplicates: Exclude Classes	Specify the classes to be excluded while processing instances for duplicate CIs.
	Orphans: Exclude Classes	Specify the classes to be excluded while processing instances for orphan CIs. Best practice If you are using BMC Service Request Management for your use cases, you should consider adding BMC.CORE:BMC_RequestableOffering in the list of exceptions. Service Request Management creates CIs of type BMC.CORE:BMC_RequestableOffering for work orders, knowledge articles (KAs), and so on, in the asset dataset. The default logic of CMDB dashboard parameters expects that the Service Request Management request CI (BMC.CORE:BMC_RequestableOffering) be related to CIs of type business service (BMC_BusinessService) through a weak relationship of type BMC_ServiceRealizedByOffering. But in Service Request Management use cases, the BMC_ServiceRealizedByOffering relationship is not created between the business service CI and the SRM request CI. To avoid these CIs being detected by CMDB as orphan CIs, you must add BMC.CORE:BMC_RequestableOffering in the list of exceptions.
Process duplicate CIs	Enable Duplicate Processing	If this check box is selected, enable the processing of all CIs for duplicates when the Dashboard utility is run in the KPI mode. If this check box is not selected, the Dashboard utility does not record details of duplicates and the Dashboard does not display this information. Best practice When you run the utility for the first time while enabling the processing of duplicate CIs , the execution time may be substantial, affecting database performance. We recommend that you run this utility for the first time during non-peak hours.
	Number of Classes to Process Concurrently	Specify the number of threads the dashboard utility creates to process classes for duplicate CIs. Each thread processes duplicate CIs in one class. The default value is 3 and maximum limit is 10.
	Number of Reader Threads per Class	Enter the Number of reader threads per class that the Dashboard Utility must spawn to find out duplicates per CDM class. The default value is 2 and maximum value is 10.
	Number of processor threads per class	Specify the number of threads that the dashboard utility creates to identify duplicates that the reader threads have retrieved. The default value is 2 and maximum value is 10.

Excluding classes and datasets for processing Dashboard parameters

On this page