Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

source_ip_address option enhancement #1196

Open
thatsdone opened this issue Feb 25, 2024 · 0 comments
Open

source_ip_address option enhancement #1196

thatsdone opened this issue Feb 25, 2024 · 0 comments

Comments

@thatsdone
Copy link

This is a kind of suggestion (or maybe an weak feature request).

Now we have 'source_ip_address' option for various probers.
I think it's useful to add a configration option to (at least ICMP) prober
allowing to specify interface name like '-I' option of ping.
For other applications, it's like '--interface' option of curl ,or '-B' option of ssh etc.

One of use cases is like this.
I'm working on 5G mobile networking stack, and there,
IP address(es) assigned to UE (User Equipment, simply speaking, smartphone)
change dynamically along with location of the UE.
In addition, a 5GS UE can have multiple slices. A slice is normally mapped to independent
L3(/L2) network, meaning tunnel(/tap) device.

Here, in order to monitor per slice connectivity, it's not convenient
using a predefined source_ip_address, but if we can have an option
to specify source interface like below, we can eliminate reconfigure & restart
blackbox_exporter.

https://github.com/prometheus/blackbox_exporter/blob/master/example.yml#L144

  icmp_example:
    prober: icmp
    timeout: 5s
    icmp:
      preferred_ip_protocol: "ip4"
      #source_ip_address: "127.0.0.1"
      source_interface: "tun0"  <== possible new option

I hope this makes (some?) sense.
Regards,
Masanori

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant