Network Interface - Duplicates/Nulls

Hello Justin_Lanoue, I hope this finds you well! A recent update to the "Network Interfaces" (SNMP_Network_Interfaces) module has addressed this concern.

As Anonymous has shared, you generally want ifindex persistence for SNMP enabled on your devices to prevent this, but in general, the IDs changing for interfaces can indeed cause the issues you are seeing.

To address this, add the property interface.wildvalue.ifname to your resource (or group of resources), and set the value to true.

 

https://www.logicmonitor.com/support/smnp-network-interface-monitoring#h-module-wildvalue-tracking

This will help avoid concerns with changing interface indexes. Please update your datasource, and give it a try!
https://www.logicmonitor.com/support/logicmodules/about-logicmodules/keeping-your-datasources-up-to-date 

LM creates a duplicate because that logicmodule doesn't have the "use the wildvalue as the unique identifier" checked. Which means that it doesn't just use the ID as the key for that object, it uses the combination of the id and they name. Same id but different name? LM treats it as a separate object. I'd like to see LM go through all their legacy modules and identify which ones can safely switch over to the new ID method and make the change. It wouldn't take much to evaluate a couple modules a week and push the change. It would also get/keep their "we push out updates very often" numbers up.

I don't have an answer myself but it's been brought up a few times in this community, for example at https://community.logicmonitor.com/discussions/product-discussions/how-is-everyone-else-handling-network-interface-id-changes/14445