Staleness metric calculation based on last discovered fieldIssue It is unclear whether the staleness metric can be calculated using the last discovered field instead of the sys_updated_on field. Release ALL Resolution The logic for using sys_updated_on is in the backend. This field is not customizable. The Product Documentation shows that the staleness metric uses sys_updated_on for the staleness check. Most Recent Discovery is used only by discovery, while sys_updated_on is updated by all sources, including discovery. This behaviour is inherited from the parent CMDB class. Currently, discovery updates sys_updated_on regardless of any data change, and other sources follow the same consistent behaviour. Based on this design, the product uses sys_updated_on because it provides more benefit than most recent discovery. Related Links Review CMDB health stale rule creation documentation