Capability Reporting
After onboarding, a device reports what it is — its compute resources and interfaces — so the platform knows what workloads it can run.
Who this is for: OT engineers connecting devices.
The DeviceCapabilitiesManifest
Section titled “The DeviceCapabilitiesManifest”The device submits a manifest of kind DeviceCapabilitiesManifest, with:
apiVersionkind—DeviceCapabilitiesManifestproperties— the reported resources
Reported resources
Section titled “Reported resources”Under properties, a device reports:
| Resource | Contents |
|---|---|
cpu | number of cores (and, optionally, architecture) |
memory | available memory |
storage | available storage |
peripherals | optional — list of attached peripherals |
interfaces | optional — list of network/other interfaces |
cpu, memory, and storage are always present; peripherals and
interfaces are optional.
No read-back over the Margo API
Section titled “No read-back over the Margo API”The Margo API defines no GET for capabilities — there is no endpoint to
read capabilities back through the API. A device reports its manifest (POST),
can replace it (PUT), and can unregister (DELETE) — all against the
/clients/:clientId/capabilities/:deviceId path (Margo v1.0.0-rc2). Within
Fleet Manager, the reported capabilities are surfaced on the Overview tab of
the device detail page.
Why it matters
Section titled “Why it matters”The platform uses reported capabilities to match applications to devices — for example, an application’s resource requirements and compatible-device list (see Applications) are checked against what a device reports here.