## Write the description belowThere's nothing preventing a cloudvirt from being left over in maintenance (i.e. `nova-compute` service disabled on it at the `compute service` level.
With {T424802} in place we can now do the following:
* Turn `compute service list -f json` into prometheus metrics exporting the per-host service status
* Alert when an host has `nova-compute` disabled for longer than a certain threshold
* And/or alert when an unexpected number of cloudvirts has `nova-compute` disabled
The `-f json` output looks like this:
```
{
"ID": "9e43876c-e482-461d-9ae0-ad8d1376e49e",
"Binary": "nova-compute",
"Host": "cloudvirt1080",
"Zone": "nova",
"Status": "enabled",
There's nothing preventing a cloudvirt from being left over without aggregate and/or with an unexpected (to be defined) "State": "up",
set of them. "Updated At": "2026-07-09T10:28:27.000000"
}
```
note this output includes other nova services too running on e.g. cloudcontrol
This task is to define what "unexpected aggregate" means,```
and create an alert to notify us when that happens.{
"ID": "755f82d2-62c2-4525-bbc6-8de6ce0bbb1b",
"Binary": "nova-conductor",
"Host": "cloudcontrol1006",
"Zone": "internal",
"Status": "enabled",
"State": "up",
"Updated At": "2026-07-09T10:28:31.000000"
},
```