# CPU readiness metric showing 0 in Alloy (vCenter integration) despite config changes

**URL:** <https://community.grafana.com/t/cpu-readiness-metric-showing-0-in-alloy-vcenter-integration-despite-config-changes/162699>\
**Category:** Grafana Alloy\
**Tags:** configuration, alloy\
**Created:** [April 29, 2026, 12:15pm UTC](https://community.grafana.com/t/cpu-readiness-metric-showing-0-in-alloy-vcenter-integration-despite-config-changes/162699 "2026-04-29T12:15:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stutishovanamohanty4](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@stutishovanamohanty4](https://community.grafana.com/u/stutishovanamohanty4)\
**Post date:** [April 29, 2026, 12:15pm UTC](https://community.grafana.com/t/cpu-readiness-metric-showing-0-in-alloy-vcenter-integration-despite-config-changes/162699/1 "2026-04-29T12:15:05Z")

</div>

Hello Team,  
We are facing an issue in the alloy version - v1.9.2 with CPU readiness metrics in Grafana Alloy using the vCenter integration. The data is being ingested into Mimir successfully , however the CPU readiness metric consistently reports a value of 0.

Below are the troubleshooting steps and observations so far:

1. Verified the Alloy configuration for the vCenter integration by running Alloy in debug mode; however, the root cause could not be identified.

2. Updated and re-deployed the Alloy configuration multiple times, but the issue persists.

3. Adjusted the collection interval to evaluate the impact:

4. In Splunk, the CPU readiness metric is observed in milliseconds, whereas Alloy appears to scrape and forward only percentage-based CPU readiness values.

Could you please help us with the following:

- Why is CPU readiness always reported as 0 in Alloy?
- Does Alloy support CPU readiness metrics in milliseconds for vCenter?
- Is there any specific configuration or metric mapping required to obtain accurate CPU readiness values?

---

<div class="post-metadata">

**Author:** ![aroncampbell](https://avatars.discourse-cdn.com/v4/letter/a/bc8723/32.png) [@aroncampbell](https://community.grafana.com/u/aroncampbell)\
**Post date:** [May 4, 2026, 3:50am UTC](https://community.grafana.com/t/cpu-readiness-metric-showing-0-in-alloy-vcenter-integration-despite-config-changes/162699/2 "2026-05-04T03:50:37Z")

</div>

Hi Community,

Looking for feedback from anyone who has implemented the vcenter receiver and is actively looking at this data in alloy or the downstream contrib collector.

For reference this is on the vcenter receiver configuration and the specific metric in Mimir is vcenter\_vm\_cpu\_readiness\_percent

This is documented on this page: [otelcol.receiver.vcenter | Grafana Alloy documentation](https://grafana.com/docs/alloy/latest/reference/components/otelcol/otelcol.receiver.vcenter/)

| `vcenter.vm.cpu.readiness` | [`metric`](https://grafana.com/docs/alloy/latest/reference/components/otelcol/otelcol.receiver.vcenter/#metric) | Enables the `vcenter.vm.cpu.readiness` metric | | | |
| --- | --- | --- | --- | --- | --- |

In the collector contrib [opentelemetry-collector-contrib/receiver/vcenterreceiver/documentation.md at v0.147.0 · open-telemetry/opentelemetry-collector-contrib · GitHub](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/v0.147.0/receiver/vcenterreceiver/documentation.md)

It is described as **vcenter.vm.cpu.readiness**

Percentage of time that the virtual machine was ready, but could not get scheduled to run on the physical CPU. It is a gauge type of metric.

This value is expected to be non-zero but it is returned for all VM in all vcenter instances as a zero value.

The vcenter cluster version is v8 family and all other metrics are being received with no issues It literally is just this metric but it is an important metric nontheless.

Regards,

Aron