Disscussions moved from issue #8 about problems on CentOS 8 about traceroute-map-panel

[Gowee]

(To keep the discussion separated from the other issue, I am opening a new issue here.)

@cddisk2000

Hi. I have looked through your blog post where the image shown under "#查詢「mtr」資料表 及前「5」筆資料。" implies the data has already been collected correctly.

I can see only one point displayed on the map in your screenshot. I guess the problem is those ??? in the IP field, which are collected as-is from the output of mtr. ??? usually indicates that the IP address of a hop cannot be determined by mtr, which in turn indicates the hop on the path does not respond to mtr probing.

It is fine to have some ??? hops on a path. But in general, there should be several responding hops. So only one point on the map is abnormal.

More information is needed to find where the problem is. Is everything working well (at least several non-??? hops) when you manually mtr via shell? Is the mtr -C -n www.google.com output you pasted in the previous issue complete? Or could you please paste the FULL output of mtr -C -n 8.8.8.8 here?

[cddisk2000]

@Gowee
I'm just doing a sample test , In China Google can't be accessed. If it's other domain names no problem.
Traceroute map panel is sure to work properly,
By the way Use traceroute not all nodes will have feedback, depending on the ISP device
Thank you for developing this plug-in

Centos7 needs to install MTR 0.94 to support the output format,But I can't find CentOS 7 to install MTR 0.94 version
This is the main reason

[Gowee]

The README of mtr gives concise instructions to install from the source. It should work well on CentOS 7 where I have tested.

It is also possible to make telegraf adapted to the other output format by tweaking its config as I said in #8 (comment).

Feel free to leave comments here if you encounter other problems.

[cddisk2000]

@Gowee
CentOS 7 to install mtr v0.94 from the source succeeded。
Thank you very much

[Gowee]

I am happy to hear that.

I will update the README to mention the MTR version requirement.

For better tracking issues, I am going to close this for now. If you have other problems, just reopen it by replying again.