Collectd
VictoriaMetrics
Collectd | VictoriaMetrics | |
---|---|---|
7 | 97 | |
2,989 | 10,900 | |
0.7% | 2.3% | |
9.2 | 9.9 | |
7 days ago | about 22 hours ago | |
C | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Collectd
-
μMon: Stupid simple monitoring
https://collectd.org/ does the gathering (and writing to RRDTool database, if you so desire) part very well. Many plugins, easy to add more (just return one line of text)
Still need RRD viewere but that's not a huge stack
And it scales all the way to hundreds of hosts, as on top of network send/receive of stats it supports few other write formats aside from just RRD files.
-
Post Mortem on Mastodon Outage with 30k users
Then you will have same problems but now you can bother manufacturer about it!
Also unless there is something horribly wrong about how often data is written, that SSD should run for ages.
We ran (for a test) consumer SSDs in busy ES cluster and they still lasted like 2 years just fine
The whole setup was a bit of overcomplicated too. RAID10 with 5+1 or 7+1 (yes Linux can do 7 drive RAID10) with hotspare woud've been entirely fine, easier, and most likely faster. You need backups anyway so ZFS doesn't give you much here, just extra CPU usage
Either way, monitoring wait per drive (easy way is to just plug collectd [1] into your monitoring stack, it is light and can monitor A TON of different metrics)
* [1]https://collectd.org/
-
IT Pro Tuesday #217 - Python Frameworks, Logging Tutorial, Android Terminal & More
Collectd pulls metrics from the OS, applications, logfiles and external devices for use in monitoring systems, finding performance bottlenecks and capacity planning. hombre_sabio explains, "Collectd is a tiny daemon that gathers information from a system. It enables mechanisms to collect and observe the values in different techniques. It is an open-source monitoring tool to retrieve and manage SNMP master agents."
-
PHP7.4 Installation Fail
Setting up php7.4-fpm (7.4.25-1+deb11u1) ... Job for php7.4-fpm.service failed because a fatal signal was delivered to the co ntrol process. See "systemctl status php7.4-fpm.service" and "journalctl -xe" for details. invoke-rc.d: initscript php7.4-fpm, action "start" failed. ● php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor pre set: enabled) Active: failed (Result: signal) since Mon 2021-12-27 23:53:51 GMT; 215ms ag o Docs: man:php-fpm7.4(8) Process: 2755 ExecStart=/usr/sbin/php-fpm7.4 --nodaemonize --fpm-config /etc /php/7.4/fpm/php-fpm.conf (code=killed, signal=ILL) Process: 2756 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/ph p/php-fpm.sock /etc/php/7.4/fpm/pool.d/www.conf 74 (code=exited, status=0/SUCCES S) Main PID: 2755 (code=killed, signal=ILL) CPU: 281ms Dec 27 23:53:51 raspberrypi systemd[1]: Starting The PHP 7.4 FastCGI Process Man ager... Dec 27 23:53:51 raspberrypi systemd[1]: php7.4-fpm.service: Main process exited, code=killed, status=4/ILL Dec 27 23:53:51 raspberrypi systemd[1]: php7.4-fpm.service: Failed with result ' signal'. Dec 27 23:53:51 raspberrypi systemd[1]: Failed to start The PHP 7.4 FastCGI Proc ess Manager. dpkg: error processing package php7.4-fpm (--configure): installed php7.4-fpm package post-installation script subprocess returned error exit status 1 Setting up collectd (5.12.0-7.1) ... Job for collectd.service failed because a fatal signal was delivered to the cont rol process. See "systemctl status collectd.service" and "journalctl -xe" for details. invoke-rc.d: initscript collectd, action "restart" failed. ● collectd.service - Statistics collection and monitoring daemon Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor prese t: enabled) Active: activating (auto-restart) (Result: signal) since Mon 2021-12-27 23: 53:52 GMT; 200ms ago Docs: man:collectd(1) man:collectd.conf(5) https://collectd.org Process: 2768 ExecStartPre=/usr/sbin/collectd -t (code=killed, signal=SEGV) CPU: 24ms dpkg: error processing package collectd (--configure): installed collectd package post-installation script subprocess returned error e xit status 1 dpkg: dependency problems prevent configuration of openmediavault: openmediavault depends on collectd; however: Package collectd is not configured yet. dpkg: error processing package openmediavault (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: php7.4-fpm collectd openmediavault E: Sub-process /usr/bin/dpkg returned an error code (1)
-
CPU Performance of a docker minecraft java server on Raspberry Pi 4
For metrics storage I'm using a Graphite database and the graph UI itself is Grafana. To get these I'm using the Debian repos they supply with mostly off-the-shelf configs. For collecting metrics from the Pi to send to Graphite I use collectd. It has a lot of off-the-shelf plugins you can use to grab metrics like CPU usage & load average, network in/out, memory stats etc. The Minecraft-specific stuff you can get from configuring collectd plugins as well, like the tick lag graph I use the "tail" plugin to follow and parse the server log.
-
Lightweight alternative to Grafana
For monitoring, personally I use collectd and Collectd Graph Panel (sadly the latter is abandoned, but it still works fine)
VictoriaMetrics
-
OpenTelemetry Is Too Complicated
VictoriaMetrics CTO here.
The referred library is the official OpenTelemetry package for reading metrics in Go language [1] - more details are available at [2].
Note that we at VictoriaMetrics like the idea of unified observability standard like OpenTelemetry. The issue is in the current otel implementation. It is too bloated and very inefficient. This contradicts to our experience with observability cases, which need very optimized format for metrics' transfer in order to reduce costs on CPU and network traffic needed to transfer and process these metrics.
VictoriaMetrics continues investing in OpenTelemetry by providing integration docs [3] and improving the existing functionality for otel metrics' ingestion [4].
[1] https://github.com/open-telemetry/opentelemetry-proto-go
[2] https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2570...
[3] https://docs.victoriametrics.com/guides/getting-started-with...
[4] https://github.com/VictoriaMetrics/VictoriaMetrics/issues/60...
-
Observability at KubeCon + CloudNativeCon Europe 2024 in Paris
Victoria Metrics
- All you need is Wide Events, not "Metrics, Logs and Traces"
-
Top 11 Grafana Alternatives in 2023
VictoriaMetrics is primarily a time-series database designed for efficiently storing and querying time-series data. It is often used as a back-end data store for time-series data generated by monitoring systems like Prometheus. VictoriaMetrics excels at handling large volumes of time-series data, offering efficient storage and query capabilities.
-
InfluxDB CTO: Why We Moved from Go to Rust
Not sure I follow since there are very competitive tools written in Go such as https://victoriametrics.com for an example in this space.
-
μMon: Stupid simple monitoring
Did you try VictoriaMetrics [1] and vmagent [2]? It is a single self-contained binary without external dependencies. It requires relatively low amounts of CPU, RAM, disk space and disk IO, and it runs on ARM.
[1] https://github.com/VictoriaMetrics/VictoriaMetrics/
[2] https://docs.victoriametrics.com/vmagent.html
-
CERN swaps out databases to feed its petabyte-a-day habit
https://github.com/VictoriaMetrics/VictoriaMetrics#cardinali...
If I understanding correctly, it deal with high cardinality by dropping data, the operators need to monitor for this and adjust their data to lower the cardinality.
-
Prometheus Observability Platform: Intro
VictoriaMetrics
-
VictoriaMetrics VS openobserve - a user suggested alternative
2 projects | 30 Aug 2023
-
OpenTelemetry in 2023
You shouldn't unless you want to use the new open source standard for telemetry. You won't benefit from simplicity or performance improvements. It would be quite the opposite. You can check what is the actual cost of open telemetry adoption here [0]
But if you ever decide to go this path - VictoriaMetrics supports OpenTelemetry protocol for metrics [1]
[0] https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2570
[1] https://docs.victoriametrics.com/Single-server-VictoriaMetri...
What are some alternatives?
Telegraf - The plugin-driven server agent for collecting & reporting metrics.
mimir - Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
prometheus - The Prometheus monitoring system and time series database.
thanos - Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
Collectl - Extending collectl to send process data to graphite
Statsd - Daemon for easy but powerful stats aggregation
loki - Like Prometheus, but for logs.
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.
ClickHouse - ClickHouse® is a free analytics DBMS for big data
Ganglia - Ganglia Web Frontend
InfluxDB - Scalable datastore for metrics, events, and real-time analytics