How to work on Orphan CIs metric on CMDB WOrkspace

[Lucky1]

Spoiler

Hi all,

In the CMDB workspace, I understood Duplicate CIs and De-Duplication tasks. But not understanding how this Orphan CIs and Stale CIs will work here. Where they got configured.

Because, From the list of Orphan CIs, I have taken one CI and created a relationship with a server. Yet it is still showing in the orphan CIs list. Not understanding why.

1) Can someone explain me how this works here?

2) What's new frame. How to activate New CIs, New applications, New Hardware etc, on this frame. Why they are showing 0.

Please help me.

[Pratiksha]

Stale CIs are configuration items that haven’t been updated within a specified time period. For example, if a device is discovered today but is not updated afterward, it becomes stale. You can track such CIs using the CI Class Manager. To configure this:

1. Navigate to CI Class Manager.

2. Open the class you want to monitor.

3. Click on Health on the left-hand side.

4. Set the number of days to define when a CI should be considered stale.

Orphan CIs, on the other hand, don’t require any configuration. These are CIs that have lost their parent relationship. For instance, if a switch is deleted but its associated switch ports remain in the CMDB, those ports are considered orphaned CIs.

[Lucky1]

Hi Pratiksha,

I see Orphan CIs from the Dashboard will go away if they come out of the Orphan rules we created in CI class manager.

I welcome your insights on this.

Regards,

Lucky