[–] siliconc0w 11y ago ↗ also https://github.com/google/cadvisorwhich now supports native export to influxdb [–] bbrazil 11y ago ↗ Apparently influxdb would take 11x the storage of prometheus's approach: http://prometheus.github.io/docs/introduction/comparison/#pr... [–] jrv 11y ago ↗ (Prometheus author here)Yeah, InfluxDB is great, but suits slightly different use cases than Prometheus. That is, monitoring numeric time series vs. event logging, basically. Still, I could well imagine running both in a single organization for these different needs.
[–] bbrazil 11y ago ↗ Apparently influxdb would take 11x the storage of prometheus's approach: http://prometheus.github.io/docs/introduction/comparison/#pr... [–] jrv 11y ago ↗ (Prometheus author here)Yeah, InfluxDB is great, but suits slightly different use cases than Prometheus. That is, monitoring numeric time series vs. event logging, basically. Still, I could well imagine running both in a single organization for these different needs.
[–] jrv 11y ago ↗ (Prometheus author here)Yeah, InfluxDB is great, but suits slightly different use cases than Prometheus. That is, monitoring numeric time series vs. event logging, basically. Still, I could well imagine running both in a single organization for these different needs.
[–] jrv 11y ago ↗ See also SoundCloud's post about releasing Prometheus today: https://developers.soundcloud.com/blog/prometheus-monitoring...
5 comments
[ 2.8 ms ] story [ 23.1 ms ] threadwhich now supports native export to influxdb
Yeah, InfluxDB is great, but suits slightly different use cases than Prometheus. That is, monitoring numeric time series vs. event logging, basically. Still, I could well imagine running both in a single organization for these different needs.