CMDB Health Dashboard and SCCM - SCCM CI's Showing as Stale

Maurice Murphy
Tera Guru

My organization is standing up Discovery, and previously our only use of our CMDB was populating computer records via Service Graph for SCCM. There's no concerns with the SCCM CI's, but now that we are discovering more CI's and are starting to utilize the health dashboard, it appears that all of the computer records are showing as stale. 

 

Is there a way to make it so these CI's don't show as stale other than excluding them from the health dashboard? My org is considering computers to be a principal class, and they want them to appear on the dashboard even if they're coming from SCCM and not Discovery.

1 ACCEPTED SOLUTION

MattSN
Mega Sage
Mega Sage

OOB all records that have not been updated for 60 days or more meet the criteria of stale.

MattSN_0-1688640450643.png

 

If the SCCM plugin is still functional, the active records should get updated with a new "Most recent discovery" timestamp with each run. This would also update the sys_updated_on value for the record which should exclude it from the stale filter.

 

You could create your own staleness rule on the computer class as an alternative option.

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/configuration-management/ta...

View solution in original post

2 REPLIES 2

MattSN
Mega Sage
Mega Sage

OOB all records that have not been updated for 60 days or more meet the criteria of stale.

MattSN_0-1688640450643.png

 

If the SCCM plugin is still functional, the active records should get updated with a new "Most recent discovery" timestamp with each run. This would also update the sys_updated_on value for the record which should exclude it from the stale filter.

 

You could create your own staleness rule on the computer class as an alternative option.

https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/configuration-management/ta...

Spot on MattSN. That's just what I was about to recommend and that's how you should solve this @Maurice Murphy