3 ms·

The problem I have with Prometheus is, I have most of my nodes in very closed networks I don't have control (Healthcare) and I can't set up proxies so Prometheu

The problem I have with Prometheus is, I have most of my nodes in very closed networks I don't have control (Healthcare) and I can't set up proxies so Prometheus can reach them, I can only go outside. So, by now, my best option seems to be InfluxDB, which doesn't look bad to me.

linsomniac 8y ago
I've been using InfluxDB for ~3 years now for storing metrics (almost exclusively via Telegraf, a few custom ones), and it has been great! It replaced a collectd setup and dramatically decreased load across my fleet. When I first started using it, it was pretty early and had some issues. In fact, I nearly trashed it. I also didn't like the pull vs. push model from Prometheus. They ended up resolving the InfluxDB issues I was having right as I was about to give up on it, and it's been solid since. I use it with Grafana to generate graphs of system use. I set it up before TICK was a thing.
- h1d 8y ago
  I was about to like InfluxDB but ever since people say it eats memory and your data, I stopped caring. https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/FAQ https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/FAQ ("How does VictoriaMetrics compare to InfluxDB?")
  - linsomniac 8y ago
    That hasn't been my experience. I've been running it for ~3 years in our dev, stg, and prod environments. Prod is using 1.5GB of RAM on a 5GB instance. I've never had a data loss issue.
h1d 8y ago
Push gateway? https://prometheus.io/docs/instrumenting/pushing/ https://prometheus.io/docs/instrumenting/pushing/
valyala 7y ago
I'd recommend giving a try to VictoriaMetrics. It requires less hardware resources - RAM, CPU, disk - comparing to InfluxDB [1] and it supports PromQL - much nicer query language for typical time series queries comparing to InfluxQL or Flux [2]. It may be used as a drop-in replacement instead of InfluxDB on the ingestion path [3]. [1] https://medium.com/@valyala/insert-benchmarks-with-inch-influxdb-vs-victoriametrics-e31a41ae2893 https://medium.com/@valyala/insert-benchmarks-with-inch-infl... [2] https://medium.com/@valyala/promql-tutorial-for-beginners-9ab455142085 https://medium.com/@valyala/promql-tutorial-for-beginners-9a... [3] https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Single-server-VictoriaMetrics#how-to-send-data-from-influxdb-compatible-agents-such-as-telegraf https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Sing...

linsomniac 8y ago

I've been using InfluxDB for ~3 years now for storing metrics (almost exclusively via Telegraf, a few custom ones), and it has been great! It replaced a collectd setup and dramatically decreased load across my fleet. When I first started using it, it was pretty early and had some issues. In fact, I nearly trashed it. I also didn't like the pull vs. push model from Prometheus. They ended up resolving the InfluxDB issues I was having right as I was about to give up on it, and it's been solid since. I use it with Grafana to generate graphs of system use. I set it up before TICK was a thing.

h1d 8y ago
I was about to like InfluxDB but ever since people say it eats memory and your data, I stopped caring. https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/FAQ https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/FAQ ("How does VictoriaMetrics compare to InfluxDB?")
- linsomniac 8y ago
  That hasn't been my experience. I've been running it for ~3 years in our dev, stg, and prod environments. Prod is using 1.5GB of RAM on a 5GB instance. I've never had a data loss issue.

h1d 8y ago

Push gateway? https://prometheus.io/docs/instrumenting/pushing/ https://prometheus.io/docs/instrumenting/pushing/

valyala 7y ago

I'd recommend giving a try to VictoriaMetrics. It requires less hardware resources - RAM, CPU, disk - comparing to InfluxDB [1] and it supports PromQL - much nicer query language for typical time series queries comparing to InfluxQL or Flux [2]. It may be used as a drop-in replacement instead of InfluxDB on the ingestion path [3]. [1] https://medium.com/@valyala/insert-benchmarks-with-inch-influxdb-vs-victoriametrics-e31a41ae2893 https://medium.com/@valyala/insert-benchmarks-with-inch-infl... [2] https://medium.com/@valyala/promql-tutorial-for-beginners-9ab455142085 https://medium.com/@valyala/promql-tutorial-for-beginners-9a... [3] https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Single-server-VictoriaMetrics#how-to-send-data-from-influxdb-compatible-agents-such-as-telegraf https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Sing...