Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upRelabel consul node to instance not working #2539
Comments
This comment has been minimized.
This comment has been minimized.
|
This is a known bug in 1.5.0, please upgrade to 1.5.2. |
brian-brazil
closed this
Mar 29, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
perbly commentedMar 28, 2017
As you see in the picture, instance-label isn't the __meta_consul_node. But when i do a mouseover the nodename is correct.
And it seems like reconfiguring/restarting prometheus gives the correct nodename for a while and then it just disappear and becomes the address:post again.
I tried to relabel __meta_consul_node to a new label called "hostname" and that worked perfect for a while also until it just disappeared.
What did you do?
Configured prometheus to scrape consul and relabel _consul_node to instance
What did you expect to see?
the nodename (hostname)
What did you see instead? Under which circumstances?
address+port
Environment
Consul 0.7.3
System information:
Ubuntu 16.10
Prometheus version:
1.5.0
Alertmanager version:
insert output of
alertmanager -versionhere (if relevant to the issue)Prometheus configuration file: