CMDB Health system properties

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    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

    This document outlines the configuration of system properties that enable ServiceNow customers to customize the monitoring and evaluation of Configuration Items (CIs) health within the CMDB Health module. The settings help optimize performance and allow for tailored logging and auditing processes.

    Show full answer Show less

    Key Features

    • Max Running Time: Sets the maximum time (in minutes) for individual metric processors to run during scheduled cycles. Default is 120 minutes; exceeding this halts processing until the next job.
    • CI Ownership Attribute: Defines the attribute in the [cmdbci] table that links to User or User Group tables, impacting dashboard ownership displays.
    • Logging Levels: Configures the level of logging for CMDB Health jobs, which aids in debugging by capturing health auditing messages. Default is 'error'.
    • Audit Source Control: When enabled, only displays health results from CMDB Health audits, excluding results from other sources like Cloud Discovery.
    • Staleness Exclusion: Allows customers to exclude dependent CIs from staleness checks, enabling more focused health assessments.

    Key Outcomes

    By configuring these properties, customers can enhance the efficiency and accuracy of CI health monitoring. This customization leads to more reliable health metrics and streamlined auditing processes, ultimately improving the overall management of their CMDB.

    Configure the following system properties to customize how CMDB Health monitors and evaluates CIs health.

    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 pane, select 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.

    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 All > Configuration > Health Preference. In the right hand-side pane, select System Properties.
    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.