# Cpu metrics values higher than expected

**URL:** <https://discuss.hashicorp.com/t/cpu-metrics-values-higher-than-expected/61095>\
**Category:** Nomad\
**Created:** [December 21, 2023, 11:29am UTC](https://discuss.hashicorp.com/t/cpu-metrics-values-higher-than-expected/61095 "2023-12-21T11:29:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gary.bright](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/gary.bright/32/43835_2.png) [@gary.bright](https://discuss.hashicorp.com/u/gary.bright)\
**Post date:** [December 21, 2023, 11:29am UTC](https://discuss.hashicorp.com/t/cpu-metrics-values-higher-than-expected/61095/1 "2023-12-21T11:29:56Z")

</div>

Hi there

I’m using Prometheus to scrape my nomad clients and I’ve reviewing my jobs.

In particular I was trying to graph the cpu its used, I used ‘nomad.client.allocs.cpu.total\_percent’ and ‘nomad.client.allocs.cpu.total\_ticks’ The problem that I’m see is that the raw values look to exceed the physical specs of the machine.

Does anyone know how this can be?

for example total\_ticks should be MHz and the host client machine has 4 cpus totaling 10396MHz yet I have data points in the 13k.

Any ideas?

Gary