Thomas Casteleyn
Thomas Casteleyn
Maybe a good idea to start working with GitHub milestones again for these kind of tasks?
On [Slack](https://influxcommunity.slack.com/archives/CH99HUH8V/p1679384697164639) we only discussed for a plugin that can do trace routes natively instead of via the exec command. Response time and health can already be done via existing...
For the `ping` input we currently use [pro-bing](https://pkg.go.dev/github.com/prometheus-community/pro-bing), and it seems you can already set an TTL with that one, so it should be possible to implement a traceroute with...
Sure, let us know if it doesn’t work out, we can look for alternatives or solutions.
If it could be like you showed as example in “Additional info”, that would be great! Just be sure to emit a metric for every hop.
There is no mtr or trace route related plugin yet, You are free to go ahead 😉
For info, telegraf changes: https://github.com/influxdata/telegraf/compare/v1.18.1...v1.18.2, gosnmp changes: https://github.com/gosnmp/gosnmp/compare/v1.30.0...v1.31.0
@SuperQ, @TimRots could you have a look as well?
What about https://github.com/gosnmp/gosnmp/blob/f6c004e14098996fd473bcb322fbc8947e33f65a/marshal.go#L303-L306 versus https://github.com/gosnmp/gosnmp/blob/5160c2c028ca49af840a9c1ba56319f8e8fcb11b/marshal.go#L343-L344 This is a relevant change between these 2 versions..
Yeah indeed, but the version before did `break waitingResponse` and user says telegraf does return data in that case. I agree the device is probably returning strange results. I asked...