community VS VictoriaMetrics

Pros are instant HA and Migration. Cons are huge bandwidth hits. With your 4x1gbe you would be maxed out on replicating those 25 VMs. You wouldn't have anything for users. I have a test lab with 4 nodes, 22cpu 100gbram and 30tb space, using low end stuff, 12hdds. Proxmox, ceph dashboard, (the native ceph dashboard you can turn on), and a netdata.cloud account. So I watch it like a hawk and like to load test.

Docker-compose, not k8s. Set up a script to update the OS, pull all your containers and reboot after hours once a week or once a day. Make sure the script specifies non interactive. Set up alerting for low disk space, see https://netdata.cloud or use your own tool

There can be some issues if you mix and match elastic versions, wazuh versions, logstash versions. But the documentation guides you very well with matrix of what is and is not compatible. You will want a beefy VM to run it in, I started smaller than I should of, and after running a while it kind of puked on itself, certain things would randomly stop working. After giving it 32GB RAM, plenty of disk 4TB, and 8 vcpu, it now runs like a top. of course you will need to run, test and tune all the config files for Ossec, Wazuh, Logstash etc. The big one being JVM heap memory settings, larger these can be, the better performance. Also if you can, run it on SSD disk, helps alot being there is lots of I/O, log ingestion, processing etc. One free Linux monitoring platform I use, which I highly recommend for all Linux servers is netdata.cloud. Awesome, awesome, awesome! It actually helps tune and get real time health of the Wazuh server, and can point out pain points with hardware being undersized for example, too much swap utilization, disk I/O etc. Regardless, check that out regardless.

$ brew info netdata netdata: stable 1.29.3 (bottled) Diagnose infrastructure problems with metrics, visualizations & alarms https://netdata.cloud/ Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/netdata.rb License: GPL-3.0-or-later ==> Dependencies Build: autoconf ✘, automake ✘, pkg-config ✔ Required: json-c ✘, libuv ✘, lz4 ✘, [email protected] ✔ ==> Caveats To start netdata: brew services start netdata Or, if you don't want/need a background service you can just run: /usr/local/opt/netdata/sbin/netdata -D

Try netdata.cloud

What I know is that each node's data is still primarily stored on the node itself, and I've figured that the Registry used by Netdata cloud stores only URLs and randomly generated UUIDs. So my question is, will any other data be stored outside of my nodes? Does Netdata Cloud have access to my servers 24/7 or only when I got a browser tab with Netdata cloud open? Is there more information on security and data collection (besides GDPR and personal data collection) available on your site, netdata.cloud?

StatsD in Netdata

hey, sorry about taking so long to reply, and thanks for opening an issue on Gitlab. I just released v1.0.0 of https://xsrv.readthedocs.io/en/latest/ and will try to send a PR to https://github.com/netdata/community/tree/main/netdata-agent-deployment explaining how to bootsrap netdata from the ansible monitoring role in the coming weeks.

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.

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

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.

VictoriaMetrics

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