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
We are using Scaleway instances with routed IPs. Due to how routed IPs work, those instances have no private IPs.
The documentation says that the Scaleway SD uses the public IPv4 address by default. We have relabelled the instances to use their public IPv4 instead.
What did you expect to see?
We expect our instances with routed IPs to show up in Scaleway's service discovery with their public IP as addresses.
What did you see instead? Under which circumstances?
Instances with routed IPs (and therefor no private IPs) are not listed at all.
System information
Linux 5.15.150.1-microsoft-standard-WSL2 x86_64
Prometheus version
prometheus, version 2.51.2 (branch: main, revision: b938bbc11169dc224c103bec32a55daad0f3f34e)
build user: root@desktop
build date: 20240416-17:19:29
go version: go1.22.0
platform: linux/amd64
tags: netgo,builtinassets,stringlabels
What did you do?
We are using Scaleway instances with routed IPs. Due to how routed IPs work, those instances have no private IPs.
The documentation says that the Scaleway SD uses the public IPv4 address by default. We have relabelled the instances to use their public IPv4 instead.
What did you expect to see?
We expect our instances with routed IPs to show up in Scaleway's service discovery with their public IP as addresses.
What did you see instead? Under which circumstances?
Instances with routed IPs (and therefor no private IPs) are not listed at all.
System information
Linux 5.15.150.1-microsoft-standard-WSL2 x86_64
Prometheus version
Prometheus configuration file
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response
The text was updated successfully, but these errors were encountered: