Overriding the staleness rule, CI should change the status from retired/Non-operational to Installed

[Ashish Kumar12]

Hello Experts,

We have made an integration with the help of Service Graph connector. All the devices that are active at 3rd party tool(SCCM, JAMF, Armis, SolarWinds etc.) are successfully coming into respective classes in CMDB, when the scheduled jobs run.

Now here the Use case for which I am looking for solution:
1. If the device was populated in CMDB by this SG connector before 10 or 12 days back, but today it's not scanned by 3rd party tool, then how can we sure that CMDB data is correct.
2. If we create any staleness rule i.e. after 10 or 20 or 30 days, if this devices is not present at 3rd party tool, then mark this CI as retired or Non-operational.
3. And in another case, again after 30 days, this device is again scanned by 3rd party tool and it's up, then instead of creating a new record, it should change the status from retired/Non-operational to Installed.

Kindly suggest how can we achieve this?

In my case the 3rd part tool is Armis.

CMDB and Service Graph 

#Service graph connector

[EricDohr]

Ashish,

You may want to check out Attesting CIs 

[Ashish Kumar12]

Hi Eric,

Thanks for your reply and giving attention to my question. It looks like this is the standard practice that we can follow to find out the solution via Attesting CIs, even I am also using the same for my previous org for audit purpose. But here the case is li'l different. The customer wants that If any CI is stale for 30 or 60 days(whatever the rule they are going to set), then it should come under stale CI list. BUT if the CI again active on Armis (I am using Armis as 3rd party tool from where we are fetching the data on daily base with help of schedule job and we have already installed service graph connector) than instead of creating a new record, customer wants that the "old stale CI" should be automatically come in the respective class as installed or operation state (specially for OT classes(PLCs, SCADA servers, HMI, OT control modules, controllers etc.).

I am thinking to achieve it via some client script or may be some workflow, but I don't know which logic would be best for this.

[Anshu10]

Hi Ashish, 

Were you able to achieve your 3rd scenario. I am getting similar requirement. Would be very helpful if you could respond.