Discovery setting CIs as Absent. What's the process behind?

[mdavis933]

I need to understand if as part of the OOTB Discovery process when a CI that was previously discovered does not get discovered again the system changes the status to "Absent"

Is that something done OOTB or I might need to create my own logic for getting that done?

Thanks in advanced

[cyked · Accepted solution]

What class and what field are you referring to?

For things like running process found in an OS related to a server, those records are marked absent when discovery no longer finds them.  This might also change the status/install status/hardware status field.  They changed back to absent = false when discovered. If the host device is discovered ongoing for 30 days and the running process is still absent, the running process record is deleted.

[mdavis933]

So more specific.

On the Virtual Machine instance, I want that if Discovery no longer is able to discover a record it switches the status to Absent.

Class =cmdb_ci_vm_instance

field =install_status

[Ashutosh Munot1]

HI,

There is already a field called as Status, which will tell you if it is ON or OFF.

You have to write a logic or schedule JOB which will check the Most Recent Discovery date. If it is more that lets say 60 days or 90 days mark it as Absent.

I don't think we have something OOB.

Thanks,
Ashutosh