prometheus / prometheus/node_exporter

Ephemeral ports usage metrics

Open
#2,121 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
13.8k
Forks
2.7k
Avg merge
1d 23h
Merged PRs (30d)
8

Description

Hello,
We recently ran into an ephemeral ports exhaustion and discovered that the linux node exporter just shows data from sockstat but no details related to:

  • the ephemeral ports policy from /proc/sys/net/ipv4/ip_local_port_range
  • the ephemeral ports usage (which we check manually today using netstat)
    Would that be a good feature candidate?
    Cheers.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the Linux node exporter’s existing sockstat metrics and the values available from /proc/sys/net/ipv4/ip_local_port_range. Compare those with the ephemeral-port usage currently checked through netstat, then define metrics that cover both the configured range and its usage; done means both are exposed clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
observability, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.