prometheus / prometheus/node_exporter
The status value of TCP close_cait cannot be counted, but it actually has a value
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 8
Description
Host operating system: output of uname -a
node_exporter version: output of node_exporter --version
node_exporter command line flags
./node_exporter --collector.tcpstat
node_exporter log output
Are you running node_exporter in Docker?
What did you do that produced an error?
I want to see ' node_tcp_connection_states{state="close_wait"} 5', but it doesnt have
What did you expect to see?
node_tcp_connection_states{state="close_wait"} 5
node_tcp_connection_states{state="established"} 2
node_tcp_connection_states{state="wait_time"} 9
node_tcp_connection_states{state="fin_wait1"} 1
node_tcp_connection_states{state="syn_recv"} 1
What did you see instead?
TYPE node_tcp_connection_states gauge
node_tcp_connection_states{state="established"} 2
node_tcp_connection_states{state="wait_time"} 9
node_tcp_connection_states{state="fin_wait1"} 1
node_tcp_connection_states{state="syn_recv"} 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the node_exporter entry point enabled by --collector.tcpstat and trace how it builds the node_tcp_connection_states metric. Compare the reported close_wait state with the states currently emitted, then verify that the expected state values appear in the collector output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100