This should fix the current alerts for our RAID arrays.
It's only "should" because I can't test it proper without said
RAID arrays in the dev or staging machines.

Tom Prince authored 3 years ago and Florian Sesser committed 3 years ago

This includes the host-based metrics collector, and the VPN client setup (including key deployment).

The newer "Time Series" panel does not support two axes.

... and fix that option the other commit introduced

- Also alert on "negative" (== receiving) errors
- Use 'rate' so we can get out of the reporting if situation normalizes

Grafana 8 recommends these for added performance and capabilities.

- (tryfix) Switch to Loki datasource;
- Filter requests to metrics instead of all GET;
- Show the last week by default
- Show log times

Interesting and not quickly fixable as it looks like: the
GET ... line comes *after*  the result.  We might be logging
this wrong to begin with, but probably this is some next
gen AI line ordering intelligence

Or rather, let it listen only on localhost.
I thought Grafana needed it, or Promtail needed it, but I don't remember
clearly, the web doesn't say clearly, and on my local dev stack
Promtail/Loki seems to still work just fine without GRPC on the network.

OMG look at teh genius of it

Do some name resolution for those poor computers

Improve factoring by removing those `/etc/hosts` entries

And avoid the infinite loop @tomprince was encountering in !258

Besides migrating all charts to the faster and more capable Grafana 8
TimeSeries charting tool this mainly introduces two panels to view
the logs of PaymentServer.  It has some naive and minimal filtering
in place to only show lines that are not caused by the metrics gathering
itself or that I just deemed to be OK (like "GET" requests) so we
hopefully catch those dreaded "Unexpected Exception" lines.

Fixes privatestorageops#207.

Should be pure refactoring

This is my latest version of this, updated to work with the
packages in NixOS 21.05.

Thanks to @jcalderone for the suggestion!

Fixes privatestorageops#408

Also strip that domain component from the labels collected.

Take what I learned from @tomprince in
https://whetstone.privatestorage.io/privatestorage/PrivateStorageio/-/merge_requests/220#note_17605 :
Assigning a service a `startAt' will make timer.target start it,
no need to also have it `wantedBy' multiuser.target.

Also add megacli2prom to the path even if it should be already because
of megacli2prom.  Better be safe than sorry.

Thanks go out to @tomprince!

Tryfix the starting of the timer before tahoe is updated.

This adds a detailed dashboard for tahoe-lafs running on one node.

Thanks to @tomprince for the suggestion.