thanos VS snmp_exporter

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

Sounds like you want something like Thanos

Yes, but also no. The Prometheus ecosystem already has two FOSS time-series databases that are complementary to Prometheus itself. Thanos and Mimir. Not to mention M3db, developed at Uber, and Cortex, then ancestor of Mimir. There's a bunch of others I won't mention as it would take too long.

Long term storage all depends on your needs and sophistication. I use Thanos for our system since it has an extremely flexible scaling system. But there is also Grafana Mimir. They're both similar in that they use Prometheus TSDB format as part of the underlying storage. One nice Thanos advantage is that it does do downsampling in addition to being able to store raw metric data for a long time. It will auto-select downsampled data to make requests faster.

You can aggregate all your clusters Prometheus metrics together with a wonderful tool called Thanos. This will allow you to use just a single Grafana instance against Thanos and using a label select which cluster you wish to see metrics from. The downside of this, is that none of the Grafana dashboards from the internet will work as-is. You'll need to customize all of them for Thanos support. The other downside is, you have a single point of failure, and (see next item) you can't customize who can access what in regards to your dev vs production data/metrics/access.

Depending on how you want to set things up, you can use Thanos or Mimir to create the single-pane-of-glass view of your data.

You could look at something like Thanos and store your data in S3: https://thanos.io/

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.