node_exporter VS blackbox_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.

https://github.com/prometheus/blackbox_exporter/blob/master/...

So you need 2 modules, one for each ip version. As for autamating setting these up, we deploy our Prometheus server with salt so we can use Jinja templating in all our Prometheus config files. That really cuts down on repeating boiler plate code.

This is also interesting for other reasons; in host downtime situations you can sometime see they will drop one type of traffic and not the other.

A Pi is more than enough to run a full monitoring stack. Why reinvent the wheel?

You can also use the blackbox_exporter to probe various endpoints. But in reality, you don't need to do this most of the time since the up metric gets you what you want.

Synthetic Monitoring is the Grafana Cloud implementation. It uses the blackbox_exporter

Prometheus blackbox_exporter. Free and open source.

Check something called blackboxexporter https://github.com/prometheus/blackbox_exporter

I have seen some people doing with these traditional relational databases, and I was wondering if it could be a good fit for prometheus+grafana as I have been messing around with prometheus BlackBox exporter (https://github.com/prometheus/blackbox_exporter) for web status monitoring.

You should look into the projects https://github.com/prometheus/node_exporter and https://github.com/prometheus/blackbox_exporter

You could use prometheus as a monitoring tool, blackbox_exporter to "export" the urls to prometheus, alertmanager for notifications, and grafana for nice gui dashboards (and maybe also notifications).