[foxrob92]

Yeah, I currently work for a company that does a time series DB for industrial applications (think power generation, mining, etc).

Backfilling/inserting old data is common. Control network connectivity is not always great. Sometimes you need to do fill in old data.

Forecasts are also a common use case (e.g. forecasting grid demand/capacity), so not being able to handle future data is another limitation.

[jeremycarter]

Yeah we're not talking about buggy telemetry publishing code, we're talking about systems that could have poor connectivity that can only publish data once every 10 days (but include all samples). Seems like a massive oversight.

[foxrob92]

The other surprising factor is that a lot of heavy industry will have data going back decades. If they can't get all of that data in to timestream, that's a massive mark against it.

I'd heard that it was initially developed for a major industrial operator (sounded like it was in the resources industry though I never found out who it was for), so the lack of support for late arriving data is a big surprise. That being said, there aren't any of those companies on the customers page - maybe it was just an incorrect rumour.

[valyala]

BTW, which solution do you use for this case? Did you look at vmagent? It supports the case for collecting data from industrial appliances and uploading it to a central time series database when connection to it can be established [1].

[1] https://victoriametrics.github.io/vmagent.html#use-cases