collectd vs Checkmk: What are the differences?
collectd: 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; Checkmk: A tool for Infrastructure & Application Monitoring. It is a software developed for IT Infrastructure monitoring. It is used for the monitoring of servers, applications, networks, cloud infrastructures, containers, storage, databases and environment sensors.
collectd and Checkmk can be primarily classified as "Monitoring" tools.
Some of the features offered by collectd are:
On the other hand, Checkmk provides the following key features:
- State-based monitoring
- Log- and event-based monitoring
- Graphing and analytics
collectd is an open source tool with 2.31K GitHub stars and 1.11K GitHub forks. Here's a link to collectd's open source repository on GitHub.
What is Checkmk?
What is collectd?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Checkmk?
What are the cons of using Checkmk?
What are the cons of using collectd?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We use collectd because of it's low footprint and great capabilities. We use it to monitor our Google Compute Engine machines. More interestingly we setup collectd as StatsD replacement - all our Clojure services push application-level metrics using our own metrics library and collectd pushes them to Stackdriver