ipv6 addresses for targets throws error

[jimmidyson]

Get http://fe80::f816:3eff:fee5:a2eb:10255/metrics: dial tcp: too many colons in address fe80::f816:3eff:fee5:a2eb:10255

Are ipv6 addresses supported?

[matthiasr]

They should be … and that URL should be http://[fe80::f816:3eff:fee5:a2eb]:10255/metrics. How is this address configured? SD (which kind)?

[jimmidyson]

A new kind ;) Kubernetes discovery in PR - so need to wrap ipv6 addresses in [...]. OK let me add that in - thanks.

[juliusv]

Yup, see also https://en.wikipedia.org/wiki/IPv6_address#Literal_IPv6_addresses_in_network_resource_identifiers

[jimmidyson]

@juliusv Thanks!

[wombat]

We are running Kubernetes and Prometheus on Rackspace and for some reason, they sometimes assign ipv4, sometimes ipv6 addresses.

The example prometheus configuration for kubernetes suggests to use the kubernetes-service-endpoints job which does autodiscovery on services that should be scraped. At this point it is not possible to add any bracket to the ipv6 address and we also don´t know in advance which address will actually be used by prometheus.

From my perspective it would be good if prometheus would be smart enough to detect if its an ipv4 or ipv6 address.

Thoughts?

[jimmidyson]

Are you seeing ipv6 addresses not wrapped in [..] properly? That is a bug if so - could you open a separate issue for that please?

[wombat]

@jimmidyson No, they are not wrapped at all - will open an issue for that

UPDATE: see #1944

[lock]

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.