I have not directly been affected by this debacle, but I would like to add the
observation that I have never previously come across a professional hosting
provider who announces the closure of some service and then simultaneously
blocks access to the data (or even more extreme, turns off the servers holding
it), thereby preventing people from retreiving their historical data for some
reasonable period of time after the service itself is no longer available.
I genuinely think that InfluxDB needs to take some unplanned and possibly
rather expensive steps to reinstate the customer data which has been affected
by this appalling lack of communication, so that people can continue running
their services on-premises, at another hosting location, or with another
provider.
As @Viktor_ingemarsson put it very succinctly: “data loss is not an acceptable
option” and I think InfluxDB has to address that promptly and comprehensively.
Antony.
