We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Staleness and Orphan Rule

sntech
Tera Contributor

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.

 

 

4 REPLIES 4

maheshkhatal
Giga Sage

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
Giga Sage

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

 

 

Issue resolved? → Mark as Correct


Found value? → Mark as Helpful


@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?

 

 

drbob
Tera Contributor

"CMDB Health Dashboard" is the place to see the issues - I think you can set tasks to be triggered for some of them but if there are any that you can't then you can just write a scheduled tasks to deal with them. Probably not a good idea to switch anything on until you know the size of the "problem" - you don't want to drown people in corrective tasks.

 

Note that the staleness is measured using "sys_updated_on" - so _any_ change will keep it out of the sale list (that might not be a change that implies the system if "freshened" - maybe someone added a comment saying "this is stale but I'm not sure why" ...then it would no longer be stale, at least not for the next 60 days). If you're looking for "refreshed by discovery" I think you have to create your own tests.