71–80 of 298 posts
Really, REALLY tried to love InfluxDB. But its systems requirements, performance, and features are poor compared to things like TimescaleDB.
Earlier quoted context omitted.
Classic "two masters" problem.
This was from the CTO last week: "This work won't be landing anywhere until sometime next year and it'll be landing in our Cloud 2 offering first." So the OSS is definitely a second-class citizen. And now that they've dropped all DevRel activity, don't expect much attention for OSS Developers and users.
We continue to support all users, including OSS users, in our public Slack and Discourse, as well as Github. We have not "dropped all DevRel" activity.
I love prometheus. Its simple and the built in charts are enough without having to use Grafana on top.
I don't. It's quite difficult to do complex queries and its query language has a few gotcha. I think it's quite good and one of the best solutions today, but I look forward to something as simple and as fast, but with a proper query language.
Earlier quoted context omitted.
I'd be interested to know a bit of detail as we're looking into Grafana/Promethus a bit.
Prometheus is a very needy child in terms of data volume and hardware resources. Running it is at least one engineers' full time job- if you're a startup, you can outsource monitoring for a tiny fraction of the price, then move to Prometheus later if you are successful.
After that, we needed some more effort to scale out horizontally with Thanos, but again, once it's set up, it maintains itself.
There's also https://github.com/timberio/vector
+1 for vector. We moved from Logstash to Vector and we couldn't be happier. Logstash is awesome but its a memory hog. With Vector and Toshi you can kinda (I am not sure Toshi is as mature as Elastic) use them to replace LogStash and Elastic, the missing piece is Kibana
Really, REALLY tried to love InfluxDB. But its systems requirements, performance, and features are poor compared to things like TimescaleDB.
Really, REALLY tried to love InfluxDB. But its systems requirements, performance, and features are poor compared to things like TimescaleDB.
What about storage? We are running influxdb and we are looking for alternative. But a point where Influx is good is storage.
I love prometheus. Its simple and the built in charts are enough without having to use Grafana on top.
The question is how to do long term storage though. Something I've had a bit of trouble rationing about. Right now all of my metrics are sitting in a PVC with a 30d retention period, so we're probably fine but for longer term cold storage the options aren't great unless you want to run a custom Postgres instance with the Timescale plugin or something else more managed.
https://www.robustperception.io/scaling-and-federating-prome...
https://prometheus.io/docs/prometheus/latest/federation/
You can set up a new "cold storage" Prometheus with a longer retention that scrapes select metrics from your regular 30d Prometheus to store for longer periods of time.