node_exporter VS snmp_exporter

$ wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz $ tar -xzvf node_exporter-1.7.0.linux-amd64.tar.gz

Node Exporter

The Prometheus node_exporter can provide this information, doesn't require root. You could run it as a systemd user unit if you don't have root.

I personally find it best to learn through experimentation. Start with reading a bit about Prometheus and Grafana through their docs, and then familiarise yourself with setting up a local Prometheus + Grafana instance either locally or with docker using docker-compose, along with something to generate /metrics endpoint for Prometheus to scrape from such as a custom Prometheus exporter in Python or using Node Exporter.

Your best bet might be to fork node_exporter to get you more verbose socket stats: https://github.com/prometheus/node_exporter/blob/master/collector/sockstat_linux.go

I use Grafana + Prometheus + Node Exporter.

Crazy idea, can't NX devices run Docker? I wonder if the node_exporter would work.

Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.

You may setup node exporter and collect metrics with prometheus for example. Its not quite "simple" way, but still you may find it useful.

It is kind of described here:https://github.com/prometheus/snmp_exporter/issues/405

The SNMP exporter can do lookups. Take a look at this documentation.

wget https://github.com/prometheus/snmp_exporter/releases/download/v0.21.0/snmp_exporter-0.21.0.linux-amd64.tar.gz

You need to find the OSBs for the router, and add those to the explorer. Take a look at this doc: https://github.com/prometheus/snmp_exporter/blob/main/generator/README.md

You can fetch this metrics using the SNMP exporter https://github.com/prometheus/snmp_exporter

As a maintainer of the Prometheus SNMP exporter, and the defacto standard implementation of SNMP in Go, I can tell you exactly how convoluted SNMP is at a protocol and specification level.

Refer to https://github.com/prometheus/snmp_exporter and https://blog.paessler.com/how-to-enable-snmp-on-your-operating-system

For example, you can use unpoller to bring your unifi stuff into the same system as your SNMP data.

SNMP by itself is a rather crude protocol, with values being identified as OID (Object IDs). Those are numerical identifiers. A MIB-File contains the information on how to translate these OIDs into workable data. There is some information on how to feed these files to the exporter located here: https://github.com/prometheus/snmp_exporter/tree/main/generator

Source: I help maintain open source SNMP libraries and SNMP pollers.