gopsutil VS Netdata

The specific example I'm talking about is https://github.com/shirou/gopsutil. In the usage section the imports reference both "shirou/gopsutil/v3/mem" and "shirou/gopsutil/mem" but the GitHub project sits at "shirou/gopsutil" and the go.mod references "shirou/gopsutil/v3". How does go figure out what version it's supposed to use? And how does it figure out how to use an older version if the project root is now "gopsutil/v3"?

They use gopsutil to get the host runtime details and return them as response to HTTP requests to /status.

That might help you: https://github.com/shirou/gopsutil

Golang process metrics but cpu, io are missing for freebsd https://github.com/shirou/gopsutil

I'm trying to cross build on Linux a project which uses https://github.com/shirou/gopsutil.

Good project. One note: why you haven't used gopsutil library to extract system data?

shirou/gopsutil (Go): psutil for golang

netdata.cloud — Netdata is an open-source tool to collect real-time metrics. It's a growing product and can also be found on GitHub!

Netdata is designed with efficiency, scalability, and flexibility in mind, aiming to address most of the challenges associated with both open-source tools and commercial SaaS offerings.

Monitoring = netdata on each RPi https://www.netdata.cloud/ binded to the vpn interface being scraped into a prometeus thaons https://thanos.io/ setup with grafana to give management the Green all is good screens (very important).

We run netdata to have a bit of insight into whats happening on the 10+ dedicated servers in Falkenstein. So far we have seen a 1hour_ecc_memory_correctable about once a month. Suddenly we get 1hour_ecc_memory_correctable like every day from different servers. Any ideas why that could be happening?

Documentation and source code of this plugin: https://github.com/netdata/netdata/tree/master/collectors/systemd-journal.plugin

Home Page and source code: https://github.com/netdata/netdata

I started the discussion, and offered a solution too:

https://github.com/netdata/netdata/discussions/16136

hey - I work on ML at Netdata (disclaimer).

We have a big PR open and under review at moment that brings in a lot more logs capabilities: https://github.com/netdata/netdata/pull/13291

We also have some specific logs collectors too - i think in here might be best place to look around at the moment, should take you to the logs part of the integrations section in our demo space (no login needed, sorry for the long horrible url, we adding this section to our docs soon but at moment only lives in the app)

https://app.netdata.cloud/spaces/netdata-demo/rooms/all-node...