ProfessorProfessorThis is another area in LM long overdue for improvements and it just came up again due to the new "Gen 3" VMware datasources. In some cases, "Gen 2" datasources were split into multiple new datasources (a bit trickier to deal with), but in other casses the name was changed and either nothing else changed, or perhaps some datapoints changed. Changing the name of a datasource causes all of the following issues, probably others I am not thinking of:
* historical data loss
* reference breakage (widgets, alert rules, etc.)
* instance tuning loss (custom thresholds, instance descriptions, group tags, etc.)
It is understandable that the naming change clearly makes the DS set "go together", but the benefit of that is far lower than the problems created. If there was a method to upgrade/migrate the existing datasources so the new ones take effect without breaking stuff as I asked for in Aug 2017, that would indicate the developers understand this system is for monitoring and should not be arbitrarily broken for aesthetic reasons like in this case. I was advised by support that the solution is just "don't use the new datasources". Surely this is not a suitable answer? I have been told there is work being done on this front, but it is unclear what will come of it and when.
