Popularity
2.2
Stable
Activity
0.0
Stable
3
1
3
Code Quality Rank:
L3
Programming language: Perl
License: GNU General Public License v3.0 or later
Tags:
Metric & Metric Collection
Collectl alternatives and similar tools
Based on the "Metric & Metric Collection" category.
Alternatively, view Collectl alternatives based on common mentions on social networks and blogs.
-
Grafana
The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more. -
-
-
Telegraf
Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data. -
-
-
Dashing
DISCONTINUED. Ruby gem that allows for rapid statistical dashboard development. An all HTML5 approach allows for big screen displays in data centers or conference rooms. -
Freeboard
A damn-sexy, open source real-time dashboard builder for IOT and other web mashups. A free open-source alternative to Geckoboard. -
-
-
-
Diamond
Diamond is a python daemon that collects system metrics and publishes them to Graphite (and others). It is capable of collecting cpu, memory, network, i/o, load and disk metrics. Additionally, it features an API for implementing custom collectors for gathering metrics from almost any source. -
-
-
-
-
-
PGObserver
DISCONTINUED. A battle-tested, flexible & comprehensive monitoring solution for your PostgreSQL databases
InfluxDB high-performance time series database
Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
Promo
influxdata.com
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Collectl or a related project?
README
collectl
Extending collectl to send process data to graphite
The idea is to use collectl --export graphite,192.168.1.113 -sZ and generate graphite metrics like:
process.<CMD>.<PID>.cpu
process.<CMD>.<PID>.sys
...
process.<CMD>.cpu
process.<CMD>.sys
...
Potential problems:
- what happen when the process is runned by an interpreter (python blabla, python bleble, aggregated together?? no!)
- threads?
- aggregate info in collectl or in graphite (aggregation-rules.conf) ?
- lot of data to send to graphite
- how do you choose which subset to send?
- reused pids? (formatit.ph:9024)