influxdata/telegraf

netstat to collect tcp connections per port

Open

#9,348 opened on Jun 9, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (9,892 stars) (4,161 forks)batch import
feature requesthelp wantedsize/m

Description

Feature Request

Proposal:

I'd like to see implemented the netstat plugin to collect the connection states per port that the system/a service listens on, just like the TCPConns plugin of collectd

Current behavior:

The netstat plugin only gathers the amount of state types.

Desired behavior:

The netstat plugin gathers amount of state types per port.

Use case:

Currently we're using the collectd plugin to show us how much connections each of our dovecot backend nodes is handling. We'd like to replace this with Telegraf.

Contributor guide

Tech stack
go
Domain
backendobservabilityinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingBasic knowledge of Telegraf pluginsUnderstanding of netstat output
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by examining the existing netstat input plugin in Telegraf's repository (plugins/inputs/netstat/). Study how it currently collects aggregate state types. Then review collectd's TCPConns plugin source code for inspiration. The implementation will likely involve parsing /proc/net/tcp to extract per port connection states. Look at how other Telegraf plugins define metrics and register with the agent. Consider adding a configuration option to specify ports or ports to watch. The 2 comments may contain additional hints.
netstat to collect tcp connections per port · influxdata/telegraf#9348 | Good First Issue