tutorials_as_code VS blackbox_exporter

ElasticSearch

code lives at: https://github.com/abhishekkr/tutorials_as_code/tree/master/talks-articles/languages-n-runtimes/golang/test-to-learn

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