collectd vs Thanos: What are the differences?
Developers describe collectd as "System and applications metrics collector". collectd gathers statistics about the system it is running on and stores this information. Those statistics can then be used to find current performance bottlenecks (i.e. performance analysis) and predict future system load (i.e. capacity planning). Or if you just want pretty graphs of your private server and are fed up with some homegrown solution you're at the right place, too. On the other hand, Thanos is detailed as "Highly available Prometheus setup with long term storage capabilities".
Thanos is a set of components that can be composed into a highly available metric system with unlimited storage capacity. It can be added seamlessly on top of existing Prometheus deployments and leverages the Prometheus 2.0 storage format to cost-efficiently store historical metric data in any object storage while retaining fast query latencies. Additionally, it provides a global query view across all Prometheus installations and can merge data from Prometheus HA pairs on the fly.
collectd and Thanos can be primarily classified as "Monitoring" tools.
Some of the features offered by collectd are:
On the other hand, Thanos provides the following key features:
- Global querying view across all connected Prometheus servers
- Deduplication and merging of metrics collected from Prometheus HA pairs
- Seamless integration with existing Prometheus setups
collectd and Thanos are both open source tools. It seems that Thanos with 3.83K GitHub stars and 429 forks on GitHub has more adoption than collectd with 2.26K GitHub stars and 1.08K GitHub forks.
