shift-rmm VS Netdata

I have just published a dashboard to the grafana marketpalce that includes showing failed services. this comes with shift-mon

I love Victoriametrics and have an ansible role that setup Victoriametrics, Grafana, and Loki using podman on a Linux VM, and is super easy to run. The only thing is switching to datadog to on prem is your team might not have the time available to manage the system or setup something to watch the watcher like having the VM server send metrics to Grafana cloud.

Grafana cloud has a two week trial that should give you a good indication of what your usage is. If you have spare hardware self hosting can be easy here is my project that turns a vm into a monitoring stack based around grafana

This is query I use for host down alerts its not perfect source

Proxmox has the ability to ship metrics to influxdb or graphite without installing an agent. I use shift-mon which uses Victoriametrics and grafana under the hood

I use and love Victoriametrics, Telegraf, and grafana for monitoring proxmox, docker, and other infrastructure. Here is a repo that has an Ansible role to set all of it for you. Grafana cloud also has a free tier that is good for a lot of homelabs

I uploaded my grafana dashboard and extra config for opnsense to grafana's dashboard site. This a uses Victoriametrics for metrics, Loki for logs, and grafana for visualization. The Ansible roles to set it all up are found on gitlab

2 and 3 You can use the GUI in grafana to build Prometheus queries in grafana. I also prefer push over pull. I found out Victoriametrics is a thing and let's you push data as if it was influxdbv1 and add it to grafana as a promtheus data source. I deploy everything via ansible and here is the link to the repo

Prometheus might not be the best tool I prefer Telegraf and Victoriametrics so I can push metrics and still query it as if it where Prometheus. My setup can be found here

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