Related Lists of CI components
Summarize
Summary of Related Lists of CI components
Related Lists in Configuration Item (CI) records display additional components contained within that CI, such as disk drives on servers or rules controlling network routers. These lists are dynamically populated by Discovery scans, showing only components detected during the most recent scan. Components not found in the latest scan are considered absent and omitted from the lists.
Show less
There are two types of components shown: those that are themselves CIs (e.g., hard disks) and components that are not (e.g., serial numbers and rules). Default filters ensure that only active components (not marked as absent) are visible in the related lists.
Key Features
- Dynamically updated: Related Lists reflect the current state of CI components based on the latest Discovery scan results.
- Component types: Lists include both CI-type components and non-CI components, each filtered appropriately to exclude absent items.
- Icons indicating CI status: Various icons appear in related lists to indicate active incidents, problems, changes, outages, and downstream CI issues. These icons help quickly identify the operational status of components related to the CI.
- Teams related list: Associates user groups with CIs based on group type, helping track which teams are responsible for specific services. This appears in Service class CIs and their descendants.
What This Enables You to Do
ServiceNow customers can effectively monitor and manage the components within their CIs, ensuring visibility into the current state and health of each CI and its parts. By leveraging the Related Lists, customers can:
- Understand the makeup of complex CIs through component visibility.
- Track ongoing and planned changes, incidents, problems, and outages directly related to CI components.
- Identify downstream CI issues impacting service delivery.
- Assign and manage team responsibilities for specific services to streamline operational accountability.
Practical Considerations
Because Related Lists depend on Discovery results, the accuracy and completeness of these lists rely on regular and successful Discovery scans. Components absent in the latest scan are not shown, so discrepancies may indicate changes or issues in the environment.
The system evaluates recent and upcoming changes and outages within a timeframe of five days past and seven days future, providing timely context for operational activities.
Related lists in CI records display additional components contained by that CI, such as disk drives on a server and the rules that control the behavior of a network router.
When Discovery runs, the Related List is populated with the components that Discovery finds running on the CI. The CI record might show different lists from scan to scan, depending on whether or not Discovery found the component.
By default, the Related Lists only display those components that are associated with that CI in the CMDB that has been discovered by the last scan. Components that are recorded in the CMDB but are not discovered in a scan, are deemed absent and do not appear in the list.
There are two types of components that appear in the Related List: components that are CIs themselves (such as hard disks), and components that are not (serial numbers and rules). The default filter condition in the breadcrumbs for components that are CIs is [Status] [!=] [Absent]. The filter condition for components that are not CIs is [Absent] [=] [false].
For example, a router can have several Related Lists affected by these filter conditions, including routing rules, disk drives, interfaces, and network adapters. Only those components found during the last Discovery appear in these Related Lists.
Icons in related lists
| Icon | Description |
|---|---|
| Currently active incidents | For currently active incidents against this configuration item |
| Currently active problems | For currently active problems against the configuration item |
| Currently active changes | For currently active changes against the configuration item that are not covered in the past, current, pending changes. For example, a request to update the operating system on a server that is currently in progress may display this icon. |
| Recently completed changes | For changes that were recently completed against the configuration item. changes with an "Actual_end_date" in the past. |
| Planned changes | For changes that are planned soon against the configuration item. changes with an "Actual start date" in the future. |
| Currently active changes | For currently active changes against the configuration item that have an "Actual start date" |
| Recently completed outages | For outages that were recently completed against the configuration item. outages with an "end" date in the past. |
| Planned outages | For outages that are planned soon against the configuration item. outages with a "begin" date in the future. |
| Currently active outages | For currently active outages against the configuration item that have a "begin" date in the past and no "end" date |
| Issues with downstream CI | This will only show up in the Tree view and indicates that a configuration item that is downstream has at least one of the above issues against it. |
The system looks five calendar days into the past and seven calendar days into the future when looking at recent outages and changes.