, a dashboard that "displays a lot of data about one single host".

This is

One query for hosts with ZFS and one for those without.

Since ZoL frees ARC under memory pressure, let's not
count it as "used" but instead as "free" memory.

See similar earlier commit

maybe will reveal some useful info some day

The port is not necessarily bound by the time systemd considers the unit
started so wait for the port instead of the unit.

node_memory_MemAvailable_bytes is a better estimator than the sum I used before
says some Prometheus documentation.  It is also almost the same, but reads nicer.

This is only semi correct. We keep logs up to what's specified in the privacy
policy.  Currently, that is implemented as keeping them for up to 30 days on
the individual nodes as well as on the central Loki server.

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

Nix sometimes seems peculiar about merging sets?

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

groups based on cfg.introducers are already set up above and this expression
is clearly meant to define groups for the nodes