prometheus
Adding Network HOP Count Feature for TCP Probes
Currently, the Network HOP count feature is not natively supported for TCP probes in the blackbox exporter. We would like to request the addition of this capability.
Use Case: When running TCP tests, it would be valuable to capture and expose the number of network hops required to reach the destination. This metric would help us monitor network path changes, latency, and potential routing issues.
Impact & Value:
Provides deeper network visibility for TCP probes. Enables proactive monitoring of network topology changes. Aligns with features offered by other monitoring solutions like Datadog. Helps in troubleshooting and optimizing network performance.
Security Considerations: Implementing network hop count detection may require special privileges or root-level access, which could be a potential security blocker. We suggest providing clear documentation about the risks and exceptions, allowing users to make informed decisions based on their environment and security policies.
We believe this feature would be a valuable addition for users who rely on TCP monitoring and would enhance the overall utility of the blackbox exporter.
@roidelapluie @mem @electron0zero
Hi, this is out of scope for the blackbox exporter, this project focuses on endpoint probing.
Please use a traceroute exporter such as jefsg/traceroute-exporter or akarneliuk/prometheus-traceroute-exporter.
Also, please don't tag maintainers, OSS maintainers are volunteers, and it’s frowned upon to tag maintainers directly to get attention :)
