UIv4 instances when there are none?
Perhaps I just wasn't paying attention previously, but does the new UI show everything has an instance even when it's not a multi-instance DataSource now? Is that a recent change? It automatically jumps to the "instance" when you click on the DataSource entry so not really causing an issue but kinda threw me for a loop when I thought a DataSource I was working on was somehow creating instances when it shouldn't. Seems kinda odd and perhaps confusing when training on what instances are if everything looks like it has one.
Avoiding duplicate instances
Hi Throwing something out there for advice. There are a number of datasources that are subject to duplication of instance because you cannot safely turn on the automatically delete as legitimate instances may go down for longer than 30 days. This appears to be due to them being very dependent on the instancename, so if this is something the customer has the ability to change then it creates another instance during Active Discovery. My question is if anyone has an ideas on a complex datapoint (or some other means) that can detect that this instance has matching property to another instance. This could be say auto.device.mac_address or even the Instance Value as these always match between the duplicate instances. This is really bugging me now so I really need to find a proactive way to address them. The real downside is that you lose the historical data when it is actually the same device. What the ideal would be is if you could merge instance or at least delete the new and rename the old one to the new ones name so its not discovered again.
