prometheus / prometheus/alertmanager
hostname not supported in --cluster.advertise-address
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
What did you do?
start alert manager with --cluster.listen-address=0.0.0.0:6783 --cluster.advertise-address=alertmanager.example.com:6783
What did you expect to see?
alertmanager starting normally
What did you see instead? Under which circumstances?
error in logs, when I put ip addr instead hostname, it works.
Environment
- System information:
Linux 3.16.0-4-amd64 x86_64
- Alertmanager version:
v0.15.0-rc.0
- Logs:
level=warn ts=2018-03-02T11:58:08.434627474Z caller=cluster.go:81 component=cluster err="couldn't deduce an advertise address: failed to parse advertise addr 'alertmanager.example.com'"
level=error ts=2018-03-02T11:58:08.435012167Z caller=main.go:166 msg="Unable to initialize gossip mesh" err="create memberlist: Failed to get final advertise address: Failed to parse advertise address \"alertmanager.example.com\""
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the startup failure with the advertised hostname and the command shown in the issue. Inspect cluster.go around line 81 and the initialization path in main.go; done means a hostname in --cluster.advertise-address is accepted and Alertmanager starts normally without the reported gossip-mesh errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100