Install status as Absent

[PaulSylo]

Hello experts -

I am in the process of cleaning up my stale CI data from CMDB, while I did some basic analysis, I found more than 85K CI are in "install status = absent", I took the most recent discovery as 90 days. but no clue why this Install status becomes absent. 

1. Can you help me to understand this install status as absent 

2. How to fix this absent state, fact, 

3. Regd Stale CI, I see the option and best practice to make this stale CI as retired as it is not required or Not used now in My Org. What is the best practices, how to fix this stale CI and prevent it in future?

[Sohail Khilji · Accepted solution]

Hi @PaulSylo ,

Hope your doing well !

1. Can you help me to understand this install status as absent.

>> Let's say you own a server which has 2 disk. Disk 1 & disk 2. When discovery runs it will discovery both disk and associates it with you server.

Leter if you remove 1 disk out of it and if discovery runs and finds the disk missing or not present it will make it as absent. It simply means it was not found since X days hence marked in stale CI.

2. How to fix this absent state, fact, 

>> If they no more part of your infra you can simply remidate them as like normal retired CIs.

Check for >> CMDB Data Manager module., It provides a workflow for you and deals with your Retirement, Archival, and Deletion scenarios. 

3. Regd Stale CI, I see the option and best practice to make this stale CI as retired as it is not required or Not used now in My Org. What is the best practices, how to fix this stale CI and prevent it in future?

>>There is no prevention for stale CIs from happening , over the period of time every infra will end up having stale CI which needs to be Actioned by cmdb team for cleanup or create a automation workflow or flow to clear them out.

I hope this helps....

[Sohail Khilji · Accepted solution]

Hi @PaulSylo ,

Hope your doing well !

1. Can you help me to understand this install status as absent.

>> Let's say you own a server which has 2 disk. Disk 1 & disk 2. When discovery runs it will discovery both disk and associates it with you server.

Leter if you remove 1 disk out of it and if discovery runs and finds the disk missing or not present it will make it as absent. It simply means it was not found since X days hence marked in stale CI.

2. How to fix this absent state, fact, 

>> If they no more part of your infra you can simply remidate them as like normal retired CIs.

Check for >> CMDB Data Manager module., It provides a workflow for you and deals with your Retirement, Archival, and Deletion scenarios. 

3. Regd Stale CI, I see the option and best practice to make this stale CI as retired as it is not required or Not used now in My Org. What is the best practices, how to fix this stale CI and prevent it in future?

>>There is no prevention for stale CIs from happening , over the period of time every infra will end up having stale CI which needs to be Actioned by cmdb team for cleanup or create a automation workflow or flow to clear them out.

I hope this helps....

[Sohail Khilji]

Hi @PaulSylo ,

If the response proves usefull kindly mark the Thread as 'Accept Answer' to clear the queue...

[Amit Gujarathi]

HI @PaulSylo ,
I trust you are doing great.

1. Understanding "Install Status" as Absent: This status indicates that during recent discovery, certain CIs were not found, possibly due to changes like disk removal from a server.

2. Fixing Absent State:

   • Identify absent CIs.
   • Retire or remove them if no longer part of the infrastructure.
   • Utilize CMDB Data Manager for workflow assistance.

3. Addressing Stale CIs and Best Practices:

   • Regularly review and retire stale CIs.
   • Consider automation for identification and cleanup.
   • Proactive monitoring can help minimize future occurrences.

[Dr Atul G- LNG]

@AJ-TechTrek 

Any thoughts here?