ts=2026-07-03T22:00:45.368Z caller=main.go:181 level=info msg="Starting Alertmanager" version="(version=0.27.0, branch=rhaos-4.18-rhel-9, revision=341c4e12263f125e4234413e549e05209b22444a)"
ts=2026-07-03T22:00:45.368Z caller=main.go:182 level=info build_context="(go=go1.22.12 (Red Hat 1.22.12-1.el9_5) X:strictfipsruntime, platform=linux/amd64, user=reproducible@reproducible, date=20241016-05:16:14, tags=netgo,strictfipsruntime)"
ts=2026-07-03T22:00:45.385Z caller=cluster.go:263 level=warn component=cluster msg="failed to join cluster" err="2 errors occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 172.30.0.10:53: read udp 10.128.0.19:35773->172.30.0.10:53: read: connection refused\n\t* Failed to resolve alertmanager-main-1.alertmanager-operated:9094: lookup alertmanager-main-1.alertmanager-operated on 172.30.0.10:53: read udp 10.128.0.19:54752->172.30.0.10:53: read: connection refused\n\n"
ts=2026-07-03T22:00:45.385Z caller=cluster.go:265 level=info component=cluster msg="will retry joining cluster every 10s"
ts=2026-07-03T22:00:45.385Z caller=main.go:291 level=warn msg="unable to join gossip mesh" err="2 errors occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 172.30.0.10:53: read udp 10.128.0.19:35773->172.30.0.10:53: read: connection refused\n\t* Failed to resolve alertmanager-main-1.alertmanager-operated:9094: lookup alertmanager-main-1.alertmanager-operated on 172.30.0.10:53: read udp 10.128.0.19:54752->172.30.0.10:53: read: connection refused\n\n"
ts=2026-07-03T22:00:45.385Z caller=cluster.go:683 level=info component=cluster msg="Waiting for gossip to settle..." interval=2s
ts=2026-07-03T22:00:45.411Z caller=coordinator.go:113 level=info component=configuration msg="Loading configuration file" file=/etc/alertmanager/config_out/alertmanager.env.yaml
ts=2026-07-03T22:00:45.411Z caller=coordinator.go:126 level=info component=configuration msg="Completed loading of configuration file" file=/etc/alertmanager/config_out/alertmanager.env.yaml
ts=2026-07-03T22:00:45.414Z caller=tls_config.go:313 level=info msg="Listening on" address=127.0.0.1:9093
ts=2026-07-03T22:00:45.414Z caller=tls_config.go:352 level=info msg="TLS is disabled." http2=false address=127.0.0.1:9093
ts=2026-07-03T22:00:45.454Z caller=coordinator.go:113 level=info component=configuration msg="Loading configuration file" file=/etc/alertmanager/config_out/alertmanager.env.yaml
ts=2026-07-03T22:00:45.454Z caller=coordinator.go:126 level=info component=configuration msg="Completed loading of configuration file" file=/etc/alertmanager/config_out/alertmanager.env.yaml
ts=2026-07-03T22:00:47.386Z caller=cluster.go:708 level=info component=cluster msg="gossip not settled" polls=0 before=0 now=1 elapsed=2.000859239s
ts=2026-07-03T22:00:55.389Z caller=cluster.go:700 level=info component=cluster msg="gossip settled; proceeding" elapsed=10.003248369s
ts=2026-07-03T22:01:00.396Z caller=cluster.go:473 level=warn component=cluster msg=refresh result=failure addr=alertmanager-main-0.alertmanager-operated:9094 err="1 error occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 172.30.0.10:53: read udp 10.128.0.19:42598->172.30.0.10:53: read: connection refused\n\n"
ts=2026-07-03T22:01:00.399Z caller=cluster.go:473 level=warn component=cluster msg=refresh result=failure addr=alertmanager-main-1.alertmanager-operated:9094 err="1 error occurred:\n\t* Failed to resolve alertmanager-main-1.alertmanager-operated:9094: lookup alertmanager-main-1.alertmanager-operated on 172.30.0.10:53: read udp 10.128.0.19:54424->172.30.0.10:53: read: connection refused\n\n"
ts=2026-07-03T22:01:15.491Z caller=cluster.go:473 level=warn component=cluster msg=refresh result=failure addr=alertmanager-main-0.alertmanager-operated:9094 err="1 error occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 172.30.0.10:53: no such host\n\n"
ts=2026-07-03T22:01:30.393Z caller=cluster.go:473 level=warn component=cluster msg=refresh result=failure addr=alertmanager-main-0.alertmanager-operated:9094 err="1 error occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 172.30.0.10:53: no such host\n\n"
ts=2026-07-03T22:01:45.393Z caller=cluster.go:473 level=warn component=cluster msg=refresh result=failure addr=alertmanager-main-0.alertmanager-operated:9094 err="1 error occurred:\n\t* Failed to resolve alertmanager-main-0.alertmanager-operated:9094: lookup alertmanager-main-0.alertmanager-operated on 172.30.0.10:53: no such host\n\n"