influxdata / influxdata/telegraf

Freebsd 14 telegraf inputs.wireguard is silent.

Open
#14,397 18 comments 0 reactions 0 assignees View on GitHub
bug upstream
Dominant language
Go
Stars
17.8k
Forks
5.8k
Avg merge
1d 20h
Merged PRs (30d)
161

Description

### Relevant telegraf.conf

```toml
# 3------1---------2---------3---------4---------5---------6---------7---------8
# 2023.12.07 test
# 3------1---------2---------3---------4---------5---------6---------7---------8
#
[[inputs.wireguard]]
# does this work?
devices = ["wg0", "wg1"]
```

### Logs from Telegraf

```text
2023-12-07T05:01:28Z I! Starting Telegraf 1.21.4
```

### System info

Telegraf 1.21.4, freebsd, FreeBSD 14.0-RELEASE

### Docker

_No response_

### Steps to reproduce

1. create simple config based on: https://github.com/influxdata/telegraf/tree/release-1.21/plugins/inputs/wireguard
2. , above config is in telegraf.conf.TEST here.
3. /usr/local/bin/telegraf --config=/usr/local/etc/telegraf.conf --config-directory=/usr/local/etc/telegraf.conf.TEST --test --debug

4.
...

### Expected behavior

results of some sort as per the documentation.

### Actual behavior

silence

### Additional info

Both wg0 and wg1 exist, but even removing the "devices =" line produces only silence.

Contributor guide

Open the contributing guide

Research direction

Start with the inputs/wireguard plugin at the release-1.21 path referenced in the report, then reproduce on FreeBSD 14 using the shown telegraf.conf and command. Compare behavior with and without devices = ["wg0", "wg1"]. Done means the test run produces wireguard results as documented, or clearly reports why collection cannot proceed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking, observability, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.