compute

GET /v1/compute/servers/{serverId}/health

Read a server's hardware and live resource usage.

Gbogbo àwọn compute endpoints

Ìfàṣẹ́pọ̀

Fi bọ́ọ̀lù (bearer token) ranṣẹ gẹ́gẹ́ bí kọ́kọ́rọ́ API. Kọ́kọ́rọ́ náà gbọ́dọ̀ ní ìyọ̀ǹda sites.view; a ó kọ̀ ọ́ silẹ pẹlu 403, kii ṣe 404, ti kọ́kọ́rọ́ náà kò bá ní i.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

curl -X GET https://api.zinndigital.com/v1/compute/servers/{serverId}/health \
  -H "Authorization: Bearer zdk_live_…"

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

What the machine is made of - cores, memory, disk, operating system - and how hard it is working right now: CPU, memory, disk and this month's bandwidth. Read live from the provider on every call and never stored, for the same reason the renewal is: a cached CPU reading is stale the moment it is written, and a customer looking at a usage gauge is asking about now. Every usage figure is `-1` when the provider did not answer, which is **not** the same as zero. A client must render the difference: `0%` says the machine is idle, `-1` says we could not ask. Memory and disk are byte counts with both halves of the ratio, so a screen can say "224 MB of 1 GB" rather than only a percentage. `power_state` is the provider's own word (`running`, `shut off`), carried verbatim and never rounded to a boolean. This response deliberately carries **no hostname**. The provider also states the guest hostname and the physical KVM host; both name our supplier and are never exposed to a customer. Requires `sites.view`.

Àwọn ìpìlẹ̀

OrúkọIruTí a nílòKini o jẹ
serverId (path)UuidBẹẹniThe server's id, as `listComputeServers` reports it. **Ours** (UUIDv7), minted when the order row was written — never the provider's own identifier for the machine.

Idahun

OrúkọIruTí a nílòKini o jẹ
coresintegerBẹẹniVirtual CPU cores the machine is sold with.
ram_mbintegerBẹẹniMemory the machine is sold with, in megabytes.
disk_gbintegerBẹẹniPrimary disk the machine is sold with, in gigabytes.
os_namestringBẹẹniThe provider's own name for the operating system image, or `""`.
ram_used_bytesintegerBẹẹniMemory in use, in bytes. `null` when the provider did not say.
ram_total_bytesintegerBẹẹniTotal memory, in bytes. `null` when the provider did not say.
disk_used_bytesintegerBẹẹniDisk in use, in bytes. `null` when the provider did not say.
disk_total_bytesintegerBẹẹniTotal disk, in bytes. `null` when the provider did not say.
cpu_percentnumberBẹẹniProcessor in use, 0-100. `null` when the provider did not say. ⛔ **Normalised to a real percentage at the boundary, on every range.** One provider reports every non-idle CPU cla…
bandwidth_used_gbnumberBẹẹniThis month's transfer, in gigabytes. `null` when not stated.
bandwidth_allowance_gbnumberBẹẹniThe monthly transfer allowance, in gigabytes. ⭐ **The one field on this schema that may be `-1`**, meaning the allowance has no ceiling; `null` means the provider did not state…
bandwidth_overage_gbnumberBẹẹniTransfer used beyond the allowance this month, in gigabytes, as the provider states it — the figure overage charges are computed from. `null` when not stated, and a client must…
power_statestringBẹẹniThe provider's own word for the machine's state (`running`, `shut off`), verbatim and never rounded to a boolean, or `""`.

Awọn aṣiṣe ti ibudo ipari yii le da pada

401 · 403 · 404 · 422 · 429 · 503