David Heap

Hi, Thanks for getting back to me - this is for a stack with a separate controller and 3 servers. The controller is only connected to the `caddy-controller` network, and...

Thanks for looking into this - as the ingress is also in the overall /17 we've decided to keep specifying the /24 range for now to keep configuration access locked...

It's standalone

No, we're not seeing high resource usage of any kind, and the server has not been put into service yet so has no clients connected to it. It does seem...

We saw the same thing with: `/path/to/promtail -config.expand-env=true -config.file /etc/promtail.yml` ``` scrape_configs: - job_name: journal journal: labels: hostname: ${HOSTNAME} ``` The `hostname` label ends up blank

Also would there be a way to have different behaviour for silenced vs active alerts? e.g. silenced ones are collapsed and active ones are expanded?

We're seeing the same issue with the `/metrics` endpoint when running Alloy 1.3.1-1 via a systemd service directly on servers (as a replacement for promtail). It looks to happen in...

Actually on further testing mine seems to be broken by the second stage.labels stanza - changing it to the following fixes the issue on restart: ``` stage.labels { values =...

We're seeing the same issue on registration (screenshot shows next page after entering email address for email auth), but only when specifying a longer password. - A 16 character password...

When we tried reinstalling with a shorter password we also saw the same error after installation, configuration and a reboot, the db resource looked like this until we'd done a...