-
Notifications
You must be signed in to change notification settings - Fork 63
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
if network_exporter can support the latest functions of mtr #27
Comments
I don't understand what you mean by TCP protocol in relation to MTR, I checked the mentioned exporter and its not doing anything different. |
@syepes Sorry for not describing it clearly, I mean the mtr mode of network_exporter, can it support the tcp protocol and the specified port like the mtr command line tool. Because we have a scenario where the use of ping is prohibited, but the telnet port can be used. Now I want to test it through mtr. If the port is blocked, which hop route is the problem. |
I have encountered the same problem. Do you have a solution? |
We need this too. Our network treats ICMP and TCP differently. Especially sometimes packets are routed base on hash(src_ip,src_port,dst_ip,dst_port), however this does not hold for ICMP. |
MTR --tcp feature will be very helpful for debugging network issues. |
@syepes it would be nice to have MTR running TCP probes, as described in the issue here. Thanks. |
Currently, I don't have sufficient time to extensively explore the TCP implementation. Although I have attempted to do so before, I have found it to be quite complex. Of course any PR's are welcome :-) |
a great exporter!! its really helpfull! Thanks a lots. |
hi @syepes :
The new mtr currently supports the TCP protocol, and also supports the specified TCP port. I don't know if network_exporter can support the latest functions of mtr.
This can be referred to, mtr-exporter
https://github.com/mgumz/mtr-exporter
The text was updated successfully, but these errors were encountered: