Why node_cpu_seconds_total of one core is greater than elapsed time

[Casin Zhao]

When i run the query : node_cpu_seconds_total{instance="1.1.1.1", cpu="9"} -   node_cpu_seconds_total{instance="1.1.1.1", cpu="9"} offset 1m  and i got result greater than 60s.

[Casin Zhao]

Update: the version of my environments

os: centos 6.1

node_exporter: 1.0.1

[Brian Candler]

If your server has multiple cores, then it can run more than 1 second's worth of CPU activity in 1 second.  That's expected.

BTW you do realise that CentOS 6 has gone end-of-life?  https://wiki.centos.org/About/Product

[Ben Kochie]

By how much? 

If you query for `node_cpu_seconds_total{instance="1.1.1.1", cpu="9"}[5m]`, what are the raw sample results?

On Tue, Aug 24, 2021 at 11:02 AM Casin Zhao <cas...@gmail.com> wrote:

When i run the query : node_cpu_seconds_total{instance="1.1.1.1", cpu="9"} -   node_cpu_seconds_total{instance="1.1.1.1", cpu="9"} offset 1m  and i got result greater than 60s.

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/e3472381-de46-4621-8304-872d7f7e0516n%40googlegroups.com.