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. Zipkin vs collectd

Zipkin vs collectd

OverviewComparisonAlternatives

Overview

collectd
collectd
Stacks98
Followers156
Votes5
GitHub Stars3.3K
Forks1.3K
Zipkin
Zipkin
Stacks199
Followers152
Votes10
GitHub Stars17.3K
Forks3.1K

collectd vs Zipkin: 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, Zipkin is detailed as "A distributed tracing system". It helps gather timing data needed to troubleshoot latency problems in service architectures. Features include both the collection and lookup of this data.

collectd and Zipkin can be primarily classified as "Monitoring" tools.

collectd and Zipkin are both open source tools. It seems that Zipkin with 11.4K GitHub stars and 2.07K forks on GitHub has more adoption than collectd with 2.28K GitHub stars and 1.09K GitHub forks.

Exoscale, AdStage, and Warby Parker are some of the popular companies that use collectd, whereas Zipkin is used by Medidata Solutions, Bluestem Brands, and Finciero. collectd has a broader approval, being mentioned in 14 company stacks & 33 developers stacks; compared to Zipkin, which is listed in 6 company stacks and 10 developer stacks.

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

Detailed Comparison

collectd
collectd
Zipkin
Zipkin

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.

It helps gather timing data needed to troubleshoot latency problems in service architectures. Features include both the collection and lookup of this data.

fast;simple;integrated;easy to operate
-
Statistics
GitHub Stars
3.3K
GitHub Stars
17.3K
GitHub Forks
1.3K
GitHub Forks
3.1K
Stacks
98
Stacks
199
Followers
156
Followers
152
Votes
5
Votes
10
Pros & Cons
Pros
  • 2
    Modular, plugins
  • 2
    Open Source
  • 1
    KISS
Pros
  • 10
    Open Source

What are some alternatives to collectd, Zipkin?

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.

Prometheus

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

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

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