influxdata/telegraf
Auf GitHub ansehenInputs PF should provide rule specific information
Open
#8.786 geöffnet am 2. Feb. 2021
area/iotfeature requesthelp wantedsize/m
Repository-Metriken
- Stars
- (9.892 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 2T 12h) (136 gemergte PRs in 30 T)
Beschreibung
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).