CMDB Health system properties
Summarize
Summary of CMDB Health System Properties
This guide outlines the configuration of system properties that enhance how CMDB Health monitors and evaluates the health of Configuration Items (CIs). These settings are primarily for users with the roles ofsncmdbadminoritiladmin.
Show less
Key Features
- Max Running Time for Metric Processor: This property determines the maximum time (in minutes) a metric processor can run during each scheduled cycle. The default is 120 minutes; exceeding this halts processing until the next job. Adjusting this value impacts performance.
- CI Ownership Field: Customize the attribute in the [cmdbci] table that indicates CI ownership, which is used in the CMDB Health Dashboard. The default is managedbygroup.
- Logging Control: Configure logging levels for CMDB Health jobs, with options including error, info, and warn. This helps in debugging issues during the health auditing process.
- Audit-Only Results: When enabled, this property restricts health results to only those identified by CMDB Health audits, excluding other sources like Cloud Discovery.
- Staleness Exclusion for Dependent CIs: This option allows you to exclude dependent CIs from staleness checks, which can simplify the evaluation of health for primary CIs.
Key Outcomes
By configuring these properties, ServiceNow customers can tailor the CMDB Health monitoring process to align better with their organizational needs, ensuring more accurate health evaluations and improving overall CI management. These configurations help in optimizing performance, enhancing logging capabilities, and focusing on relevant health metrics.
Configure the following system properties to customize how CMDB Health monitors and evaluates CIs health.
Role required: sn_cmdb_admin or itil_admin
| 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.
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.
|
| 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'.
|
| 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.
|
| 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.
|