Hello,

Can you attach a screenshot with the history of CI attribute change ? For description or DiscoveredOsName.In order to see what jobs update the attributes.

If you disabled(set to false) setting "datain.always.update.datastores.skip.reset.loa.priority" any attribute can still be updated by the datastores from setting datain.always.update.data.stores (UCMDB-UI, UCMDB, Enrichment). Also the priority will reset.

The priority will not reset anymore if this setting is set to TRUE. Note that setting name is skip.reset...

Or just remove all values from datain.always.update.data.stores.

Based on the configuration provided if node description  is updated from UI then any job can change it.

Hope it helps,

Best Regards,

Okay, I have misunderstood the meaning of the setting then. So if i set it to TRUE it will not reset the priority.

I was wondering with the names in datain.always.update.data.stores. Seeing as "UCMDB" is listed, does that mean that any UCMDB discovery will always be able to update any attribute? Is there any other implications if you remove the names from the data.stores?

Hello,

All discovery jobs are reported by UCMDBDiscovery internal dataSource. UCMDB is used for other internal updates.

If you set to empty the setting datain.always.update.data.stores there are no side effects. CIs would not be updated from UI, Enrichments  or internal UCMDB tasks in same cases, depending on the configuration.

In your screenshot I did not see any of the datastores from datain.always.update.data.stores to update DiscoveredOsName.

Is more likely that you need to add  more discovery jobs to attribute reconciliation priority for DiscoveredOsName.

Enabling debug loglevel for reconciliation logs can show more details.

Best Regards,

Thank you for your quick respons and great feedback

Best regards