Wow, the incredibly callous 3-word explanation of the issue by pointing to a docs link with no other context. Really gives off "it's your fault for not reading the wiki." Is this how InfluxDB treats their customers?
Incidentally at work we've been evaluating a new hosted observability provider, looks like we can rule out Influx as an option.
> Really gives off "it's your fault for not reading the wiki." Is this how InfluxDB treats their customers?
I don't see any indication that the person who posted that is associated with InfluxDB. In fact, it doesn't seem like any staff member has posted in that forum in the past week. Up to you if you consider that better or worse.
It's weekend and I assume people designated to answer questions on forums do not work 24/7.
It could be them not sending notification about it early enough or at all, it could be that note being stuck in spam or something, it could be person complaining not reading the e-mails.
I used Influx Enterprise at a previous startup. Support was so bad after our first year we switched back to the OSS Influx and added HAProxy with manual replication and round robin load balanced. Was so much smoother, wish we had done that from the start since that was our original plan.
Incidentally at work we've been evaluating a new hosted observability provider, looks like we can rule out Influx as an option.