| 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 |
| 10 Apr 2026 |
|  paul joined the room. | 14:02:15 |
|  Jon Zuk joined the room. | 20:57:31 |
| 11 Apr 2026 |
|  Lukas joined the room. | 02:15:00 |
| 12 Apr 2026 |
|  leona changed their profile picture. | 12:15:51 |
| 13 Apr 2026 |
|  TikTorchic18 joined the room. | 01:11:19 |
| 15 Apr 2026 |
|  @kix:matrix.kixago.com left the room. | 07:15:06 |
| 16 Apr 2026 |
|  Pascal Sthamer joined the room. | 07:04:57 |
 jaredmontoya | I had to set a GOMEMLIMIT of 120MiB, and systemd now reports 154MB usage on my server and 64MB usage on the RPI.
If I set GOMEMLIMIT to 50MB it hogs the cpu in a cycle of freeing and allocating the memory that it wants to use so unfortunately it can't be as light as promtail was (in fact it's a roughly 2.5x ram usage increase on the raspberry pi that doesn't have RAM to spare), but at least it's manageable now. | 09:33:15 |
| jaredmontoya | by the way, promtail had something called "positions file" which let it only send new logs to loki even if it was restarted. does alloy do something like this by default or I need to configure it explicitly? | 09:34:23 |
| jaredmontoya | * | 09:34:50 |
 K900 | It does by default | 09:40:34 |
|  TyIsI joined the room. | 23:14:03 |
| 17 Apr 2026 |
|  c4lliope set a profile picture. | 08:36:52 |
| c4lliope changed their profile picture. | 08:41:46 |
|  dish [Fox/It/She] changed their profile picture. | 16:58:37 |
| 18 Apr 2026 |
 sss | Failed assertions:
- boot.initrd.luks.devices.<name>.preOpenCommands and postOpenCommands is not supported by systemd stage 1. Please bind a service to cryptsetup.target or cryptsetup-pre.target instead.
how to do it nowdays ? | 01:09:54 |
 hexa | write a systemd unit in initrd instead | 01:11:17 |
| hexa | boot.inird.systemd.services.<yourunit> = { ... } | 01:12:20 |
| hexa | I would interpret binding as using BindsTo | 01:12:58 |
 ElvishJerricco | Oh uhh "bind to" is probably a bad choice of words for the assertion message then :P | 01:16:17 |
| sss | so i need to create 2 services, one with BindsTo and second which depends on cryptsetup.target ? | 01:16:32 |
| ElvishJerricco | It's only meant to tell you to make a systemd service relative to the cryptsetup target that's relevant to you | 01:17:01 |
| hexa | was gonna say this feels not correct, but got distracted | 01:18:38 |
| sss | so.... ? | 01:19:35 |
