You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2022. It is now read-only.
first of all thx for the work you're putting into this! It helped me a lot.;)
Would it be possible to add the nodes 'real' hostname to the available metadata? E.g. for the node-exporter it would be quite useful to export the hostname used in rancher, instead of the IP (just like it is possible in kubernetes).
That way it would be easy to relabel instance to the hostname..
regards,
Roman
The text was updated successfully, but these errors were encountered:
Same problem here. The node instance ID is set by default to the container IP of the exporter, not the hostname of the actual host. It's confusing and weird.
Same problem here. The node instance ID is set by default to the container IP of the exporter, not the hostname of the actual host. It's confusing and weird.
I had the same issue, I'm now overwriting all the instance labels with the actual hostnames.
This is quite easily doable in the prometheus config by setting it onto the labels attribute:
Hi,
first of all thx for the work you're putting into this! It helped me a lot.;)
Would it be possible to add the nodes 'real' hostname to the available metadata? E.g. for the node-exporter it would be quite useful to export the hostname used in rancher, instead of the IP (just like it is possible in kubernetes).
That way it would be easy to relabel instance to the hostname..
regards,
Roman
The text was updated successfully, but these errors were encountered: