Telegraf VS VictoriaMetrics

The Telegraf (v1.27.3) Net Input Plugin only reports total numbers - i.e., total bytes received by an interface.

I need some help with Filestat - https://github.com/influxdata/telegraf/tree/master/plugins/inputs/filestat

Telegraf’s Secretstores Plugin implementation on GitHub

That's the thing, I do need network_mode: host on telegraf in order to get host network statistics. See here or here

After screwing around with it for a while, I was able to get inputs.smart working... but I'm not thrilled with the answer. According to this in order for you to get the SMART data inside a container you need to edit the sudoers file inside the container.

I’ve been using the Jolokia agent with telegraf to push JVM metrics into InfluxDB (among other things). I think it can be used with Prometheus too.

Do you mean Telegraf?

I have two devices; both are connected to a Raspberry Pi using a USB converter as Slave 1 and 2. I want to get some readings using Telegraf software https://github.com/influxdata/telegraf/tree/release-1.26/plugins/inputs/modbus (happy to try any other linux software), but I'm having trouble (I'm seriously confused to be honest) with byte_order, data_type, and input register addresses.

Yeah i think you can use the grok processor, docs found here: https://github.com/influxdata/telegraf/tree/master/plugins/parsers/grok

VictoriaMetrics is a monitoring tool and time series database. It is open-source and has a managed version.

VictoriaMetrics: An incredibly fast and scalable monitoring solution and time series database.

There are many Projects like Thanos, M3, Cortex, and Victoriametrics. But Thanos is the most popular among these. Thanos addresses these issues with Prometheus and is the ideal solution for scaling Prometheus in environments with extensive metrics or multiple clusters where we require a global view of historical metrics. In this blog, we will explore the components of Thanos and will try to simplify its architecture by building it step by step, starting with the main components. We will also have a demo using k6-metrics. Before diving into Thanos, I recommend reading our blog on Prometheus Monitoring with Prometheus if you are not already familiar with Prometheus.

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

Victoria Metrics

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.

Not sure I follow since there are very competitive tools written in Go such as https://victoriametrics.com for an example in this space.