Change Details

It seems like metricsinfra is now sometimes picking the v6 address to use when scraping dualstack instances, even though the Prometheus hosts are in the legacy VLAN. (Note that Prometheus doesn't seem to be consistent which address it's using...) Options: * Move the Prometheus servers to the dualstack VXLAN network * Patch Prometheus to add an option to only use a specific family for address discovery

It seems like metricsinfra is now sometimes picking the v6 address to use when scraping dualstack instances, even though the Prometheus hosts are in the legacy VLAN. (Note that Prometheus doesn't seem to be consistent which address it's using...) Options: * Move the Prometheus servers to the dualstack VXLAN network * Patch Prometheus to add an option to only use a specific family for address discovery * Update the config to use hostnames instead of IP addresses as scrape targets

It seems like metricsinfra is now sometimes picking the v6 address to use when scraping dualstack instances, even though the Prometheus hosts are in the legacy VLAN. (Note that Prometheus doesn't seem to be consistent which address it's using...) Options: * Move the Prometheus servers to the dualstack VXLAN network * Patch Prometheus to add an option to only use a specific family for address discovery * Update the config to use hostnames instead of IP addresses as scrape targets