My team came across a In-Memory OLTP (Hekaton) transaction issue with several of our machines showing that there were a varying number of write conflicts per machine. We do have Memory-Optimized TempDB Metadata turned on.
Since restart: 0 validation failures, 0 dependency failures, 63 write conflicts, 0 unique constraint violations.
and also the Performance message
In-Memory OLTP (Hekaton) In Use, 0% of your 2097152.00GB of your max server memory is being used for in-memory OLTP tables (Hekaton).
Should we be worried about those messages? It looks like the errors are being reported by the sys.dm_xtp_transaction_stats view, and the Microsoft definition of the "write_conflicts" is "Internal use only".