HostCoreUsageDto

HostCoreUsageDto
HostCoreUsageDto

Per-host core usage

JSON Example
{
    "agentId": "string",
    "hostname": "string",
    "vcenter": "string",
    "cpuPackages": 0,
    "physicalCores": 0,
    "topologyKnown": false,
    "minimumApplied": false,
    "chargedCores": 0,
    "lastCheckInAt": "string",
    "licensingStatus": "string"
}
string
agentId
Required  

Identifier of the registered Agent, as text

string
hostname
Required  

Hostname recorded for the Agent

string
vcenter
Optional

Identifier of the vCenter connection of the most recently observed hypervisor bound to the Agent; null when no hypervisor is bound

integer As int32 As int32
cpuPackages
Optional

Number of physical CPU packages (sockets) of the host; null when not reported

integer As int32 As int32
physicalCores
Optional

Total physical CPU cores across all packages of the host; null when not reported

boolean
topologyKnown
Required  

False when cpuPackages or physicalCores is missing or not above 0; chargedCores is then the 16-core floor

boolean
minimumApplied
Required  

True when physicalCores is below 16 per CPU package, so the charge was raised to 16 cores per package

integer As int32 As int32
chargedCores
Required  

Cores charged for the host: the larger of physicalCores and 16 per CPU package, 16 when the topology is unknown, 0 when licensingStatus is RECLAIMED

string As date-time As date-time
lastCheckInAt
Optional

Time of the last heartbeat, or the Agent's registration time when it never sent one

licensingStatus
Required  

How a registered Agent counts toward consumption

  • CONSUMING: The host's last heartbeat is within 4 times the heartbeat interval of its Group; it is charged cores
  • OFFLINE_WITHIN_THRESHOLD: The host has no recent heartbeat but its last check-in is within the inactivity window; it is still charged cores
  • RECLAIMED: The host's last check-in is older than the inactivity window; it is charged 0 cores
Enumeration: CONSUMING, OFFLINE_WITHIN_THRESHOLD, RECLAIMED