Why is the discovery_source field updating despite data precedence and refresh rules?Issue If auditing the discovery_source field, you can experience auditing pollution from the discovery_source field despite any data precedence or refresh rules set up for the primary and secondary data sources. ReleaseAnyCauseThis is due to the discovery_source attribute not being applicable to the data refresh/precedence rules. If we consider staleness rules (i.e. a CI gets stale after 5 days no update) we need to know every update received even though no field value has changed. This no-change-update at least confirms that our CI data is still correct and the CI should not become stale. Hence we need at least the time stamp as well as the discovery source being updated.ResolutionThe resolution would be to disable auditing against the discovery_source attribute.