| 9 Apr 2026 |
 monokles | If it is just monitoring for a home setup without the need for metrics, you could also just pipe journald entries of interest to something by writing a small systemd service yourself. For example, I push ssh login events on my systems to private e2ee matrix rooms.
| 10:36:35 |
|  James (setkeh) Griffis joined the room. | 10:44:52 |
 phaer | I just checked because that seemed to be rather high: alloy on my hosts eats between 40 and 65M of RAM. Granted, none of those is suuuper busy with log generation, but the journal of a private rasperry pi shouldn't be either.
Maybe it's specific rules or so? I can at least tell you it does not NEED to use that much RAM if you are otherwise happy with one of them | 15:11:54 |
|  Matthew Rappard joined the room. | 17:51:39 |
| Matthew Rappard | Feel free to loudly tell me it's a bad.
But has anyone got NixOS working on a Google Cloud Workstations
https://cloud.google.com/workstations | 17:52:19 |
 blades | In reply to @mrappard:matrix.org
Feel free to loudly tell me it's a bad.
But has anyone got NixOS working on a Google Cloud Workstations
https://cloud.google.com/workstations Not nixos, but our internal equivalent uses a lot of the same tooling and it was trivial to install nix (via determinate installer) and devenv into the the workspaces.
(I would have installed nixos, but the infra team in charge begged me not to add more distros that they’d have to test.) | 18:44:41 |
