Project

General

Profile

Bug #9139

telegraf: add ping for default gateway(s)

Added by Torben Hørup over 1 year ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Telegraf
Target version:
-
Start date:
11/20/2018
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:

Description

It would be nice if telegraf plugin could generate config lines for pinging default gateway.

there's a minor issue of finding a ping implementation that works with telegraf
https://github.com/influxdata/telegraf/tree/release-1.8/plugins/inputs/ping

History

#1 Updated by Torben Hørup over 1 year ago

Maybe a upgrade to telegraf 1.7 is sufficient to get ping working ?
From 1.7 changelog #4227: Use same flags for all BSD family ping variants.

Update: I tried installing telegraf 1.8.3 (from https://github.com/influxdata/telegraf/releases ) and ping plugin works fine now.

#2 Updated by Jared Dillard over 1 year ago

  • Category set to Telegraf

#3 Updated by Ryan Jaeb about 2 months ago

The current ping plugin works well for pinging external IPs, but it would be really nice if the local gateway(s) were a special case that collected data from dpinger. There's a forum question [1] discussing doing just that. There's also a Github Gist [2] for the implementation being talked about in that thread. I don't write any python, so I can't assess that Gist, but I've been using it on my home firewall for a couple months and, with the exception of the hiccup when pfSense's python version changed, I haven't seen any side effects.

Is there any chance of getting something like that added to the telegraf package?

1) https://forum.netgate.com/topic/142093/can-telegraf-package-gather-latency-packet-loss-information.
2) https://gist.github.com/fastjack/a0feb792a9655da7aa3e2a7a1d9f812f

Also available in: Atom PDF