Staleness and Orphan Rule

[sntech]

Hi,

I need to configure the Staleness rule and Orphan rule. I am going to discuss with respective teams about duration and conditions to define orphan CI. 

But I also need to explain what happens after defining them as stale or orphan. If any Task creates or any notification is sent.

Currently, I am exploring this.

Can anyone guide on this?

Thanks you.

[maheshkhatal]

Hello @sntech ,

       By default the staleness rule is 60 days. You can change the setting via CI Class Manager and choose the appropriate class and change the default number days. 

I don't think for Orphan and Stale rule any notification or tasks are created.

Let me know if you need any help further with this. 

Thank you,

Mahesh Khatal.

[shubhamseth]

@sntech 

By default, the Staleness rule in CMDB Health uses a 60-day threshold. If a CI has not been updated within that period, it's marked as Stale and is reflected in the CMDB Health Dashboard.

Similarly, an Orphan CI is identified based on the relationship conditions you configure for the CI class.

Out of the box, no tasks are created and no notifications are sent when a CI becomes stale or orphaned. These rules are intended to highlight data quality issues in CMDB Health.

[sntech]

@shubhamseth ,

Thanks for the reply. If notifications are not created, then how the team will get to know that their CI is marked as stale or orphan? How they can modify or make it not stale and not orphan?

Any idea on this?

[shubhamseth]

@sntech There is CMDB Health Dashboard - There is separate process which each team follow. In few cases, organisations setup CCB Board (Configuration Control Board) and this board will have one of team member from each infrastructure team and this call will be bi-weekly to go over and discuss on CMDB health dashboard. This is one of the best way to handle and review CMDB health.