Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
1–10 of 298 posts
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#2This is exactly what I have been planning to do for monitoring my two Raspberry pis. I am still debating on the metrics collector though. My workplace uses monitord for AINT and telegraf for wavefront. I have no idea how well does collectord works.
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#3Really, REALLY tried to love InfluxDB. But its systems requirements, performance, and features are poor compared to things like TimescaleDB.
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#4Nothing against choosing this set of apps really, but I'm curious why collectd and not telegraf which does the same kind of metrics probes and is a part of the TICK stack.
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#5I guess collectl + graphite is not used that much these days
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#6Really, REALLY tried to love InfluxDB. But its systems requirements, performance, and features are poor compared to things like TimescaleDB.
Does any of those matter for small-scale monitoring (say <= 10 hosts)? I've got influx sitting pretty much idle in that kind of environments and any data preprocessing / collation in grafana works just fine.
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#7Really, REALLY tried to love InfluxDB. But its systems requirements, performance, and features are poor compared to things like TimescaleDB.
Influx is really shitting the bed with how they're handling the InfluxDB 2.0 release. The docs are a mess, and the migration tool seems like the result of a weekend hackathon. They're leaving a lot of customers with long term metrics in a tough spot.
If you're thinking about using Influx for long term data storage, look elsewhere. The company continuously burns customer goodwill by going against the grain, and bucking the ecosystem by trying to control the entire stack.
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#8I'm curious why they chose CollectD and not Prometheus or another pull-based ("scraping") solution. Pulling is more compositional than pushing and requires fewer machines to be touched when monitoring configuration is changed.
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#9Really, REALLY tried to love InfluxDB. But its systems requirements, performance, and features are poor compared to things like TimescaleDB.
Does any of those matter for small-scale monitoring (say <= 10 hosts)? I've got influx sitting pretty much idle in that kind of environments and any data preprocessing / collation in grafana works just fine.
Sure, if you're really not doing anything with it, then any database would work fine for you.
Re: Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD
#10Nothing against choosing this set of apps really, but I'm curious why collectd and not telegraf which does the same kind of metrics probes and is a part of the TICK stack.
As somebody new to both, are you able to elaborate on what telegraf/TICK provides that the collection of programs in the post does not?
I see lots of posts complaining about the stack in the post, but all of the alternatives posed don't really explain why.