Re:InfluxDB 1.1: 60% performance increase and new query func...
by ckdarby on Saturday December 03, 2016 @12:36AM
(#13094504)
Currently using internally for production level work. They need to spend serious time making it easier to diagnose issues when they happen.
The log is simply not verbose enough and when I hit issues with telegram, kapacitor and influxdb I have to open up a github issue having no idea what is causing the issue.
Still highly recommended they just need to spend time making it easier to identify common problems. It'll help reduce the number of github issues they have opened too.
The log is simply not verbose enough and when I hit issues with telegram, kapacitor and influxdb I have to open up a github issue having no idea what is causing the issue.
Still highly recommended they just need to spend time making it easier to identify common problems. It'll help reduce the number of github issues they have opened too.