Hacker News new | comments | show | ask | jobs | submit login

As someone who is struggling with issues with InfluxDB in production environments, this just moved my `Investigate replacing Influx with Timescale` issue higher up my priority list. Many of the problems with InfluxDB pointed out in the article are indeed real-world pain points for us.

What sort of issues are you running in to?

After running InfluxDB in production for a bit more than year, here's some issues from top of my mind we ran have into:

# Common - All: Various documentation issues

  - Including versioning in the documents
- Influx/Kapacitor: Cannot join values in Influx, but you can Kapacitor (but not dynamically)

  - Available in InfluxDB 1.6. now!
# InfluxDB

- Influx: GroupTag not grouping https://github.com/influxdata/kapacitor/pull/1773

- Influx: last() is really slow https://github.com/influxdata/influxdb/issues/8997

- Influx: Cannot update / edit tags https://github.com/influxdata/influxdb/issues/3904

- Apparently you can have tags and fields with the same names which bump up the query times by 1000x times, without ever knowing what's wrong (fixable by adding ::tag to the value)

- Cannot incrementally restore incrementally backed up databases (we made a script to do that) https://github.com/motleyagency/influxdb-incremental-restore

# Kapacitor

- Kapacitor does not support subqueries

- Kapacitor does not (properly) support queries from multiple measurements

- Cannot have field and tags with same name - Cast syntax doesn't work either (https://github.com/influxdata/influxdb/pull/6529)

# Telegraf

- Telegraf: Telegraf HTTPJson plugin does not support custom timestamps

# Chronograf

- The TickScript editor sometimes hangs for good and requires Chronograf restart

- Minor: No up-to-date syntax highlighting for TickScript in any common editors

That said we most likely would have ran into similar issues with out time series databases and I applaud their effort to keep InfluxDB open source.

In addition to the problems in the article (no mirroring, no HA, etc) it will simply stop responding seemingly randomly, and produce no errors. Have to restart the container to get it to respond again, which breaks other things.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact