--- sourceDocument: Brazil ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # CMDB Health system properties # CMDB Health system properties {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of CMDB Health system properties CMDB Health system properties allow ServiceNow customers to customize how the CMDB Health application monitors and evaluates the health of Configuration Items (CIs). These properties control processing time, ownership references, logging levels, data sources for health KPIs, and rules for staleness metrics. Proper configuration ensures efficient monitoring, accurate reporting, and effective troubleshooting within your CMDB. Show full answer Show less ## Key Properties and Their Practical Use * **Maximum Metric Processor Running Time (\[glide.cmdb.health.metricProcessor.maxRunningTime\])**: Sets the maximum run time (in minutes) for each metric processor cycle. The default and recommended maximum is 120 minutes to maintain performance. If processing exceeds this time, CMDB Health pauses until the next scheduled job. This helps avoid long-running processes that could impact system stability. * **CI Ownership Attribute (\[glide.cmdb.health.ciownershipfield\])** : Defines the attribute in the `cmdbci` table that links CIs to their owners, typically referencing users or user groups. The default is `managedbygroup`. This is vital for CMDB Health Dashboard charts to correctly display CI ownership and accountability. * **Logging Level Control (\[glide.cmdb.logger.usesyslog.CMDBHealth\])** : Configures logging verbosity for CMDB Health jobs by specifying log levels such as `error`, `info`, and `warn`. Using a comma-separated list or '' to log all levels aids in debugging and monitoring CMDB Health job execution. * **Audit Source Filtering (\[glide.cmdb.health.src.cmdbhealthauditonly\])**: When set to true, CMDB Health dashboard KPIs include only results from CMDB Health audit, excluding other sources like Cloud Discovery. This setting refines KPI accuracy by focusing exclusively on CMDB Health audit outcomes, useful when you want to isolate audit-specific health data. * **Staleness Metric Exclusion (\[glide.cmdb.health.stalenessexcludedependentcis\])**: Controls whether dependent CIs are excluded from staleness evaluation. Enabling this prevents dependent CIs from being checked for staleness, regardless of staleness or inclusion rules, helping to tailor staleness metrics to your organizational needs. ## How to Access and Configure All these system properties can be accessed and modified by users with `sncmdbadmin` or `itiladmin` roles through the `sysproperties.list` table or via the Health Preference settings under `All > Configuration > Health Preference`. Proper adjustment of these properties enables you to optimize CMDB Health processing, reporting, and diagnostics according to your environment and requirements. Configure the following system properties to customize how CMDB Health monitors and evaluates CIs health. Role required: sn_cmdb_admin or itil_admin {#r_CMDBHealthProperties__table_m5n_sk3_m5__entry__2} | Property | Description | |-|-| | Max time in minutes for which individual metric processor will run in each scheduled cycle \[glide.cmdb.health.metricProcessor.maxRunningTime\] | If processing of a metric exceeds the specified time, CMDB Health processing halts until the next CMDB Health job is scheduled to run. * Type: integer * Default value: 120 * Location: Navigate to AllConfigurationHealth Preference. In the right hand-side pane, select System Properties. {#r_CMDBHealthProperties__ul_n5n_sk3_m5} For performance reasons, it is recommended not to set this property to a value greater than 120. Note: If you enter an invalid value, the default value is used. | | Attribute in the \[cmdb_ci\] table that references the User or User Group table. CMDB Health Dashboard charts use this attribute to determine CIs' ownership. glide.cmdb.health.ci_ownership_field | Attribute in the \[cmdb_ci\] table that the CMDB Health Dashboard uses to determine CI ownership. * Type: string * Default value: managed_by_group * Location: Navigate to AllConfigurationHealth Preference. In the right hand-side pane, select System Properties. {#r_CMDBHealthProperties__ul_yy2_pkt_pbc} | | glide.cmdb.logger.use_syslog.CMDBHealth | A comma-separated list that controls the level of logging of CMDB Health jobs. Logging creates entries in the system logs to capture messages generated by the health auditing process each time they run. This logging helps debugging if there is a failure. For example, to log error and info messages, set the value to 'error,info'. * Type: String * Default value: error * Other possible values: Comma-separated list with any of the following values: * info * error * warn {#r_CMDBHealthProperties__ul_jw1_4jg_jt} Or '\*' which is equivalent to including all possible values. * Location: System Property \[sys_properties\] table. {#r_CMDBHealthProperties__ul_azj_4dz_w5} | | glide.cmdb.health.src.cmdb_health_audit_only | When set to true, disables health results from sources other than CMDB Health audit (such as Cloud Discovery). Only results generated by CMDB Health audit appear for KPIs in the CMDB Health Dashboard. For example, by default, if a CI is determined to be stale by Discovery, then that CI is counted as stale for the correctness KPI even though CMDB Health audit didn't determine that CI to be stale. However, in this case, drilling-down the stale CIs metric, still shows those CIs in which source is Cloud Discovery. * Type: true \| false * Default value: false * Location: System Property \[sys_properties\] table. * Learn more: * [CMDB Health KPIs and metrics](https://www.servicenow.com/docs/zXOtZHwL2V7brE_jVA6MrA "CMDB Health calculates an aggregated score for three Key Performance Indicators (KPIs) which are correctness, compliance, and completeness, each further consisting of sub-metrics.") * [Discovery for VMware vCenter](https://www.servicenow.com/docs/access?context=c_DiscoveryForVMwareVCenter&version=brazil&pubname=brazil-it-operations-management&ft:locale=en-US) {#r_CMDBHealthProperties__ul_jgb_lbb_zhb} {#r_CMDBHealthProperties__ul_l1g_kbf_kfb} | | glide.cmdb.health.staleness_exclude_dependent_cis | Exclude dependent CIs for the staleness CMDB Health metric. When enabled, dependent CIs are not checked for staleness, regardless of any staleness or inclusion rules that are defined for the respective CI types. * Type: true \| false * Default value: false * Location: System Property \[sys_properties\] table. {#r_CMDBHealthProperties__ul_yxq_4bb_zhb} | [Note: To open the System Property \[sys_properties\] table, enter sys_properties.list in the navigation filter.] {#r_CMDBHealthProperties__table_m5n_sk3_m5} *[\>]: and then