influxdata/telegraf

Inputs PF should provide rule specific information

Open

#8,786 opened on Feb 2, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (4,161 forks)batch import
area/iotfeature requesthelp wantedsize/m

Repository metrics

Stars
 (9,892 stars)
PR merge metrics
 (Avg merge 2d 12h) (136 merged PRs in 30d)

Description

Currently the PF input plugin only provides PF overall stats.

It would be great to have an option to also collect the output of 'pfctl -v -s rules' which are per rule statics.

(Example)

pass in log quick on vmx5 inet proto udp from <metergw> to <DiscovergyNTP> port = ntp keep state label "aaf67e315d4f23fcfd11353735e8a90b"
  [ Evaluations: 14733     Packets: 148       Bytes: 11248       States: 0     ]

I would be good to collect the (label,Evaluations,Packets,Bytes,States) tuple.

The data enables monitoring of specific communications. In my specific use case I want to see whether specific IoT devices are up (have States>0), are continously interchanging data (Packet counter steadily increasing over time).

Contributor guide

Research direction
Examine the existing PF input plugin in Telegraf, understand its structure, and identify where to add an option to collect per rule statistics by executing 'pfctl v s rules' and parsing the output.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoTelegraf plugin development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60