CMDB Health system properties

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 1 minute to read

    • Configure the following system properties to customize how CMDB Health is monitored and evaluated.

    Role required: itil_admin

    Note:
    To open the System Property [sys_properties] table, enter sys_properties.list in the navigation filter.
    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 All > Configuration > Health Preference. In the right hand-side navigator, click System Properties.

    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.
    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

      Or '*' which is equivalent to including all possible values.

    • Location: System Property [sys_properties] table.
    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.

    • Type: true | false
    • Default value: false
    • Location: System Property [sys_properties] table.