prometheus / prometheus/node_exporter
Even though node_intr_total metrics is of counter type, it's value reduced
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 csd01lab-ddeio-0 3.10.0-1160.15.2.el7.x86_64 #1 SMP Thu Jan 21 16:15:07 EST 2021 x86_64 x86_64 x86_64 GNU/Linux
node_exporter version: output of node_exporter --version
node_exporter, version 1.0.1
Are you running node_exporter in Docker?
No. node_exporter is run on VNF based on openstack
What did you do that produced an error?
No specific scenario.
What did you expect to see?
node_intr_total metrics value should have same value as that of last scrape interval OR increase.
What did you see instead?
node_intr_total metrics value reduced compared to previous value.
Is it a known issue? If yes, is fix availble in recent release?
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
Begin with the node_intr_total metric and the reported Linux 3.10 environment; compare its value across scrape intervals and check whether the behavior persists in a recent node_exporter release. Done means determining whether the decrease comes from the underlying interrupt counter or node_exporter, then documenting the finding or identifying a reproducible fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux, prometheus
- Domain
- observability, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100