-
Notifications
You must be signed in to change notification settings - Fork 2
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
Can't store data into influxdb #8
Comments
Hi, 4thdi. The config looks good. Is telegraf restarted after the config is updated? Does the log of telegraf tell anything related? And, what is the output of executing BTW, I would suggest adding an interval:
, even though it should be irrelevant to this problem. |
Thanks for your answer, it seems not working. Whether the problem is related to this configuration: "data_format"
The command result "mtr -C -n example.org":
The database query result:
The service status:
|
I think that is the problem. My output:
Try:
Their columns ( I don't have a mtr v0.85 to test. Please let me know if you find that still not working. |
Thanks a lot ! As you suggested, it's working now. Solution:
Modify the output.influxdb timeout value:
|
I am glad to hear that. There is basically no support to allow specifying geolocation data manually for now. I am willing to learn about the actual scenario you are facing. Could you please elaborate on your network architecture? For example, are all the hops (i.e. machines) with LAN IPs geographically dispersed over different places and connected via some tunnels (e.g. VPN)? Is there a known Internet IP address for each hop (even though only LAN IP is available in traceroute)? BTW, it is not necessary to increase |
Thanks for your prompt reply. There are three sites in my network topology, they are in different city, the IP address are LAN. Now the require is:
The MRT result as follows:
Hopefully this feature will be included in future releases, perhaps these requirements are out of the plug-in's design. |
Thanks for your feedback! The scenario sounds pretty reasonable. But there are some problems with the current implementation.
Setting up a custom GeoIP API could be the most feasible way. For example, on a serverless platform like Cloudflare Workers, a script can be as easy as:
Actually, line status does NOT indicate network status, at least for now. It is just a line connecting hops on a traceroute path, with fixed speed (assuming animation is turned on) and style. I was considering making line animations vary to reflect the network status (i.e. The hurdle is about both design (changing animation speed and dash length according to RTT and loss?) and implementation difficulty (say, it is somewhat infeasible to set different speeds for lines between every two hops while keeping animations smooth). |
Use Centos 7 Always Fail
|
Hi. I cannot reproduce the problem on a newly installed Would you mind opening an issue where more information can be attached? |
@Gowee
|
The telegraf config:
[[inputs.exec]]
commands=["mtr -C -n 192.168.1.2"]
timeout = "40s"
data_format = "csv"
csv_skip_rows = 1
csv_column_names=[ "", "", "status","dest","hop","ip","loss","snt","", "","avg","best","worst","stdev"]
name_override = "mtr"
csv_tag_columns = ["dest", "hop", "ip"]
[[outputs.influxdb]]
urls = ["http://127.0.0.1:8086"]
database = "my_telegraf3"
timeout = "5s"
telegraf config file testing pass, but no mtr information display:
telegraf --config /etc/telegraf/telegraf.conf --test
influxdb database creased normally, but no mtr measurement:
Using database my_telegraf3
cpu
disk
diskio
kernel
mem
processes
swap
system
Please help to resovle this problem , what should I do?
Many Thanks.
The text was updated successfully, but these errors were encountered: