Project

General

Profile

Actions

Bug #12655

open

telegraf, wireguard plugin failing

Added by Russell Morris 5 months ago.

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

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

Hi,

I'm trying to use the Wireguard plugin for telegraf, more info on the plugin here,
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/wireguard

So, I added to my telegraf "Additional configuration for Telegraf"

[[inputs.wireguard]]

But, if I then run a test (output to shell),
telegraf --test --config /usr/local/etc/telegraf.conf | grep -i wireguard

No output (just the Telegraf "header". So, I checked the Wireguard interface, with wg show, and get,
interface: tun_wg0

Adding this interface specifically to the pfSense telegraf config, it's now,
[[inputs.wireguard]]
  devices = ["tun_wg0"]

Telegraf (test) does report an output at this point, but it's not happy :-(,
2021-12-30T23:44:48Z W! [inputs.wireguard] No Wireguard device found with name tun_wg0

So something isn't quite right. I saw a similar thing before in Linux, thinking this may be related? It was tied there to user vs. kernel space implementation and access ... some links that may help here.
https://github.com/influxdata/telegraf/issues/7307
https://www.freshports.org/net/wireguard

Thoughts?

Thanks!

No data to display

Actions

Also available in: Atom PDF