Frank
8f747a2104
A socket bound to 127.0.0.1 refuses container traffic that arrives via the podman bridge: the first live webhook failed with 'dial tcp 169.254.1.2:18093: connection refused'. The relay now binds the host-gateway endpoint — link-local to the podman bridge, off the LAN — and the deployer's health probe follows it there.
30 lines
1.1 KiB
YAML
30 lines
1.1 KiB
YAML
# Alertmanager configuration for the homelab.
|
|
# Deployed to /opt/alertmanager/config/alertmanager.yml on Dankclaw.
|
|
#
|
|
# The one delivery path is Signal. The webhook lands on the host-side
|
|
# signal-relay (a systemd user unit listening on 169.254.1.2:18093, the
|
|
# host.containers.internal endpoint), which
|
|
# formats the group and hands it to signal-cli under Frank's existing
|
|
# account. There is deliberately no second receiver: a duplicate channel is
|
|
# how an alert starts arriving twice and getting muted everywhere.
|
|
#
|
|
# From this container the host's loopback is reachable only as
|
|
# host.containers.internal (169.254.1.2): netavark DNATs published ports
|
|
# only, so the host's LAN IP and the podman gateway are both refused for an
|
|
# unpublished port — the same quirk that 502'd the hermes upstream in the
|
|
# Caddyfile on 2026-09-16.
|
|
global:
|
|
resolve_timeout: 5m
|
|
|
|
route:
|
|
receiver: signal
|
|
group_by: ['alertname']
|
|
group_wait: 30s
|
|
group_interval: 5m
|
|
repeat_interval: 4h
|
|
|
|
receivers:
|
|
- name: signal
|
|
webhook_configs:
|
|
- url: http://host.containers.internal:18093/alertmanager
|