StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Monitoring
  4. Monitoring Tools
  5. Ganglia vs Prometheus vs collectd

Ganglia vs Prometheus vs collectd

OverviewDecisionsComparisonAlternatives

Overview

Ganglia
Ganglia
Stacks27
Followers88
Votes0
collectd
collectd
Stacks98
Followers156
Votes5
GitHub Stars3.3K
Forks1.3K
Prometheus
Prometheus
Stacks4.8K
Followers3.8K
Votes239
GitHub Stars61.1K
Forks9.9K

Ganglia vs Prometheus vs collectd: What are the differences?

Introduction

In the world of monitoring and performance management, there are various tools available for system administrators to choose from. Ganglia, Prometheus, and collectd are three popular tools that serve this purpose. Each tool has its unique features and capabilities, making them suitable for different use cases.

  1. Data Collection Method: Ganglia primarily uses a hierarchical design to collect and send metrics to a central server for analysis. On the other hand, Prometheus utilizes a pull-based model where each target exposes a metrics endpoint that Prometheus scrapes periodically. In comparison, collectd employs a plugin-based architecture to collect various types of system metrics and statistics.

  2. Data Storage and Querying: Prometheus has a built-in time-series database that stores all collected metrics locally, providing powerful querying capabilities using its PromQL language. Ganglia relies on RRDTool for storing historical data, making it less flexible for advanced querying. Collectd, on the other hand, lacks built-in data storage capabilities and typically forwards metrics to other tools like Prometheus.

  3. Alerting and Notification: Prometheus comes with built-in alerting features that allow users to set up rules for alert notifications based on specified conditions. Ganglia does not have native alerting capabilities and usually requires integration with third-party tools for this functionality. Similarly, collectd does not provide native alerting features and relies on external tools for setting up alerts.

  4. Community and Ecosystem: Prometheus has a rapidly growing community and a rich ecosystem of integrations with various third-party tools and platforms, making it a popular choice for monitoring in modern environments. Ganglia has a well-established community but may lack some of the modern features and integrations available in Prometheus. Collectd has a smaller community compared to Prometheus and Ganglia, which can affect the availability of plugins and support resources.

  5. Scalability and Performance: Ganglia is known for its scalability and efficiency in large-scale deployments, making it a preferred choice for monitoring clusters and distributed systems. Prometheus, while capable of handling large volumes of metrics, may require additional resources for optimal performance in high-traffic environments. Collectd is lightweight and designed for minimal resource consumption, making it suitable for monitoring individual systems or small-scale deployments.

  6. Architecture and Flexibility: Ganglia follows a client-server architecture where data is sent to a central collector for processing, while Prometheus and collectd can operate in standalone modes without the need for centralized servers. Prometheus offers more flexibility in terms of metric collection and monitoring configurations, with support for dynamic service discovery and auto-scaling environments. Collectd, on the other hand, is more focused on system-level metrics collection and may require additional tools for advanced monitoring use cases.

In Summary, Ganglia, Prometheus, and collectd each offer unique features and capabilities for monitoring and performance management, catering to different requirements in terms of data collection, storage, querying, alerting, community support, scalability, and flexibility.

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)
or
Manual

Advice on Ganglia, collectd, Prometheus

Leonardo Henrique da
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
Raja Subramaniam
Raja Subramaniam

Aug 27, 2019

Needs adviceonPrometheusPrometheusKubernetesKubernetesSysdigSysdig

We have Prometheus as a monitoring engine as a part of our stack which contains Kubernetes cluster, container images and other open source tools. Also, I am aware that Sysdig can be integrated with Prometheus but I really wanted to know whether Sysdig or sysdig+prometheus will make better monitoring solution.

779k views779k
Comments
Susmita
Susmita

Senior SRE at African Bank

Jul 28, 2020

Needs adviceonGrafanaGrafana

Looking for a tool which can be used for mainly dashboard purposes, but here are the main requirements:

  • Must be able to get custom data from AS400,
  • Able to display automation test results,
  • System monitoring / Nginx API,
  • Able to get data from 3rd parties DB.

Grafana is almost solving all the problems, except AS400 and no database to get automation test results.

869k views869k
Comments

Detailed Comparison

Ganglia
Ganglia
collectd
collectd
Prometheus
Prometheus

It is a scalable distributed monitoring system for high-performance computing systems such as clusters and Grids. It is based on a hierarchical design targeted at federations of clusters.

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.

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.

-
fast;simple;integrated;easy to operate
Dimensional data; Powerful queries; Great visualization; Efficient storage; Precise alerting; Simple operation
Statistics
GitHub Stars
-
GitHub Stars
3.3K
GitHub Stars
61.1K
GitHub Forks
-
GitHub Forks
1.3K
GitHub Forks
9.9K
Stacks
27
Stacks
98
Stacks
4.8K
Followers
88
Followers
156
Followers
3.8K
Votes
0
Votes
5
Votes
239
Pros & Cons
No community feedback yet
Pros
  • 2
    Modular, plugins
  • 2
    Open Source
  • 1
    KISS
Pros
  • 47
    Powerful easy to use monitoring
  • 38
    Flexible query language
  • 32
    Dimensional data model
  • 27
    Alerts
  • 23
    Active and responsive community
Cons
  • 12
    Just for metrics
  • 6
    Bad UI
  • 6
    Needs monitoring to access metrics endpoints
  • 4
    Not easy to configure and use
  • 3
    Supports only active agents
Integrations
No integrations availableNo integrations available
Grafana
Grafana

What are some alternatives to Ganglia, collectd, Prometheus?

Grafana

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

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.

Nagios

Nagios

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

Netdata

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

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

Sensu

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

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

Lumigo

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

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).

Jaeger

Jaeger

Jaeger, a Distributed Tracing System

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana