datasource migration function | Archive

mnagel · 2017-08-08T21:01:19Z

I have run into too many cases now where a new but slightly different DS is setup due to LM support actions, upgrades, etc. and the result is lost data or noncontinuous data. A good example I recently encountered is with NTP. The standard DS was not working in all cases. I was given a new DS that uses Groovy, and it works (which I appreciate!). But the datapoint list and names have changed, and even if they had not, there is no way to maintain data history from the old DS to the new DS. My recommendation is to add a migrate function so you can indicate how to map old to new datapoints in such a situation and thus avoid data loss. Building in a default migration ruleset into a new DS would be a bonus -- this could allow for zero-touch data migrations in at least some cases. Thanks, Mark

MoreDiscussions

datasource migration function | Archive | LogicMonitor Community