prometheus / prometheus/node_exporter
Empty reply from server in roughly every other call to the node exporter metrics endpoint
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
Linux test 3.10.0-862.el7.x86_64
node_exporter version: output of node_exporter --version
node_exporter, version 0.16.0 (branch: HEAD, revision: d42bd70f4363dced6b77d8fc311ea57b63387e4f)
build user: root@a67a9bc13a69
build date: 20180515-15:52:42
go version: go1.9.6
node_exporter command line flags
--collector.systemd --collector.supervisord
Are you running node_exporter in Docker?
No.
What did you do that produced an error?
curl localhost:9100/metrics
What did you expect to see?
All the metrics that node_exporter usually provides. This is also shown in about 50% of the requests.
What did you see instead?
About every other request returns:
curl: (52) Empty reply from server
This results in the machines flipping from UP to DOWN and back in Grafana dashboards.
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
Reproduce the failure with curl localhost:9100/metrics while using the reported --collector.systemd --collector.supervisord flags. Trace the metrics endpoint and collector behavior to determine why roughly every other request returns an empty reply; done means repeated scrapes consistently return the expected metrics without UP/DOWN flapping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100