-
Notifications
You must be signed in to change notification settings - Fork 19
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
traceroute: hosts in the route-path are not reported to Grafana Cloud #383
Comments
I'm trying to debug this. I've added some logs and |
I can't open issues in the Grafana MTR repo so I'll post it here. I've added debug logs in a bunch of places and managed to pinpoint the issue to these lines in if !bytes.Equal(sent[:4], echoPkt[:4]) {
continue
} If I comment out those lines, I see all the hosts from the route-path... but I don't know of the repercusions of doing that. Example when building with the above changes to
Let me know what you think. |
@mem tagging you here as you are the committer of the changes from my previous comment. |
@joelsdc thanks, looking |
Hi @mem, were you able to find anything? Let me know if I can help with testing or debugging. |
Hi @mem, happy new year! Do you think you can have a look at this? |
I'm going to test again with the latest 0.14.0 version and report back |
Hi @mem, any chance you can have a look at this? I've just tested on v0.14.2 and the same issue is there. |
Seems like this commit is the one that introduces the issues for me. |
Bump? :D |
Hi @mem, I'm kindly asking again if you can take a look at this, thanks! |
Hi @mem, any chance you could check my comment please? |
We have a working local instance of Grafana v8.5.15 connected to Grafana Cloud.
We have set up a private probe, and we can see the traceroute metrics, but the hosts in the path are not reported:
Notice the:
When doing a traceroute from the OS, we see all the IPs and we can ping each host in the path individually:
NOTE: IPs are masked for privacy.
Tested on v0.12.1 and v0.11.0 (in case the "update to mtr package" change from the changelog had anything to do).
I've tried also running
setcap cap_net_raw+ep /usr/bin/synthetic-monitoring-agent
but it made no difference.Any suggestions?
I'm not sure if the issue belongs here or in the
grafana/mtr
repo, if so let me know and I'll move it.Thanks!
The text was updated successfully, but these errors were encountered: