Munin vs collectd

Overview

collectd

Stacks98

Followers156

Votes5

GitHub Stars3.3K

Forks1.3K

Munin

Stacks71

Followers95

Votes10

GitHub Stars2.1K

Forks479

Munin vs collectd: What are the differences?

Data Collection Method: Munin uses a pull method where the Munin node requests data from the monitored system, while collectd uses a push method where the monitored system sends data to the collectd daemon.
Plugin Architecture: Munin has a built-in limited set of plugins for data collection, whereas collectd has a more extensive plugin ecosystem allowing for greater flexibility in data collection.
Data Storage: Munin stores historical data in Round Robin Database (RRD) files, which can lead to data loss if the files become corrupted, whereas collectd stores data in plugin-specific databases, reducing the risk of data loss.
Alerting and Monitoring: Munin focuses primarily on graphing data and lacks robust alerting capabilities, while collectd offers more advanced alerting features and can integrate with monitoring systems like Nagios.
Resource Usage: Munin is known to consume more system resources compared to collectd, making it less suitable for resource-constrained environments.
Community Support: Collectd has a larger and more active community, providing better support and more frequent updates compared to Munin.

In Summary, Munin and collectd differ in data collection method, plugin architecture, data storage, alerting capabilities, resource usage, and community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on collectd, Munin

Leonardo Henrique da

Pleno QA Enginneer at SolarMarket

Dec 8, 2020

Decided

The objective of this work was to develop a system to monitor the materials of a production line using IoT technology. Currently, the process of monitoring and replacing parts depends on manual services. For this, load cells, microcontroller, Broker MQTT, Telegraf, InfluxDB, and Grafana were used. It was implemented in a workflow that had the function of collecting sensor data, storing it in a database, and visualizing it in the form of weight and quantity. With these developed solutions, he hopes to contribute to the logistics area, in the replacement and control of materials.

403k views403k

Comments

Detailed Comparison

collectd	Munin
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.	Munin is a networked resource monitoring tool that can help analyze resource trends and "what just happened to kill our performance?" problems. It is designed to be very plug and play. A default installation provides a lot of graphs with almost no work.
fast;simple;integrated;easy to operate	-
Statistics
GitHub Stars 3.3K	GitHub Stars 2.1K
GitHub Forks 1.3K	GitHub Forks 479
Stacks 98	Stacks 71
Followers 156	Followers 95
Votes 5	Votes 10
Pros & Cons
Pros 2 Open Source 2 Modular, plugins 1 KISS	Pros 3 Good defaults 2 Adheres to traditional Linux standards 2 Alerts can trigger any command line program 2 Extremely fast to install 1 Easy to write custom plugins

What are some alternatives to collectd, Munin?

Grafana

Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins.

Kibana

Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.

Prometheus

Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

Nagios

Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License.

Netdata

Netdata collects metrics per second & presents them in low-latency dashboards. It's designed to run on all of your physical & virtual servers, cloud deployments, Kubernetes clusters & edge/IoT devices, to monitor systems, containers & apps

Zabbix

Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics.

Sensu

Sensu is the future-proof solution for multi-cloud monitoring at scale. The Sensu monitoring event pipeline empowers businesses to automate their monitoring workflows and gain deep visibility into their multi-cloud environments.

Graphite

Graphite does two things: 1) Store numeric time-series data and 2) Render graphs of this data on demand

Lumigo

Lumigo is an observability platform built for developers, unifying distributed tracing with payload data, log management, and real-time metrics to help you deeply understand and troubleshoot your systems.

StatsD

It is a network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP or TCP and sends aggregates to one or more pluggable backend services (e.g., Graphite).

Related Comparisons

Munin vs collectd: What are the differences?

Data Collection Method: Munin uses a pull method where the Munin node requests data from the monitored system, while collectd uses a push method where the monitored system sends data to the collectd daemon.
Plugin Architecture: Munin has a built-in limited set of plugins for data collection, whereas collectd has a more extensive plugin ecosystem allowing for greater flexibility in data collection.
Data Storage: Munin stores historical data in Round Robin Database (RRD) files, which can lead to data loss if the files become corrupted, whereas collectd stores data in plugin-specific databases, reducing the risk of data loss.
Alerting and Monitoring: Munin focuses primarily on graphing data and lacks robust alerting capabilities, while collectd offers more advanced alerting features and can integrate with monitoring systems like Nagios.
Resource Usage: Munin is known to consume more system resources compared to collectd, making it less suitable for resource-constrained environments.
Community Support: Collectd has a larger and more active community, providing better support and more frequent updates compared to Munin.

In Summary, Munin and collectd differ in data collection method, plugin architecture, data storage, alerting capabilities, resource usage, and community support.

Munin vs collectd

Overview