last_discovered, Data Manager Tasks and Integhub

[Tone1]

Hello Community,

I'm looking for advice on managing CI staleness detection in our CMDB.

Currently, we use Discovery and ACC-V to populate CIs, primarily Computers. We also have a Data Manager task set up to identify potentially stale CIs (PCs) by checking if the last_discovered (Most Recent Discovery) field hasn't been updated recently. If a CI is deemed stale, a retirement task is sent to the 'Managed by group' for approval.

The challenge is that we also use IntegHub ETL (via Import Sets - Excel, CSV, REST, etc.) to update other attributes on the Computer CIs daily. These IntegHub updates also update the last_discovered field. This prevents our Data Manager task from correctly identifying CIs that haven't actually been seen by Discovery/ACC for a while, as the IntegHub update resets the last_discovered timestamp.

Ideally, I'd like to prevent updates to the last_discovered field only when the update source is an Import Set (specifically, from our IntegHub jobs). I haven't found a straightforward way to configure this.

Has anyone encountered this? How can I configure ServiceNow so that only Discovery/ACC updates the last_discovered field, or how can I reliably identify stale CIs despite these IntegHub updates?

Any suggestions or alternative approaches would be greatly appreciated!

Thanks!

[Kieran Anson · Accepted solution]

Hi @Tone1 ,

For IntegrationHub, where a robust import set transformer is used, you can set a property to deactivate the behaviour of updating the last discovered timestamp.

To do this, go to the robust import set transformers table [sys_robust_import_set_transformer] and find your transformer (name will match what you called it in IntegrationHub ETL)

In the properties section, add the following, and set it to true: 'ire.skip_updating_source_last_discovered_to_now'

[Tone1]

Oh, i didnt expect to solution to be that easy. Thanks!