Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interrupts exporter does not expose interrupts for last CPU core #720

Closed
rzerda opened this issue Nov 2, 2017 · 1 comment
Closed

Interrupts exporter does not expose interrupts for last CPU core #720

rzerda opened this issue Nov 2, 2017 · 1 comment

Comments

@rzerda
Copy link

rzerda commented Nov 2, 2017

Host operating system: output of uname -a

Linux hostname 4.4.0-98-generic 121~14.04.1-Ubuntu SMP Wed Oct 11 11:54:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Also spotted on Debian Jessie.

node_exporter version: output of node_exporter --version

node_exporter, version 0.15.0 (branch: HEAD, revision: 6e2053c)
build user: root@168089f37ad9
build date: 20171006-11:33:58
go version: go1.9.1

node_exporter command line flags

--collector.interrupts

Are you running node_exporter in Docker?

No.

What did you do that produced an error?

Just run exporter and examine /metrics.

What did you expect to see?

Interrupt information for all CPU cores. My particular PC has 4 "real" cores plus HT enabled, so 8 cores total from 0 to 7.

What did you see instead?

Interrupt information for all CPU cores except the last one:

$ curl -s 'http://localhost:9100/metrics' | grep -o CPU=\"[[:digit:]]\" | sort | uniq
CPU="0"
CPU="1"
CPU="2"
CPU="3"
CPU="4"
CPU="5"
CPU="6"
@SuperQ
Copy link
Member

SuperQ commented Nov 2, 2017

Confirmed, this is a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants