OwlpaneDOCS
Operations & contracts

Device fleets (IoT beta)

Device fleets is the IoT MVP: OTLP telemetry + Postgres inventory + scorecard + risk inbox. It does not replace the Kubernetes Agent samples catalog view (node/kube metrics from the cluster agent).

Workflow

  1. Integrations → IoT — device fleets or Observability → Device fleets.
  2. Create a fleet (slug, name, optional site).
  3. Register each device (deviceId must match telemetry owlpane.device.id).
  4. Emit logs (or metrics) with the IoT telemetry contract.
  5. Open the device detail and Run scorecard, or use the Device fleet risk inbox.

Edge and collectors

Gateways often run the Owlpane agent Helm chart or any OpenTelemetry Collector forwarding to Owlpane ingest. Set resource or log attributes per the contract; see IoT edge gateway.

The cluster agent stays unchanged for K8s scraping and auto-instrumentation — that telemetry powers Agent samples, not device fleet inventory.

API

REST under /v1/orgs/:orgId/device-fleets (list fleets, register devices, scorecard, risk). Full reference: API reference.

Beta scope

Staging + Hetzner SaaS dogfood signed off 2026-10-26 (scorecard PASS). Market as beta, not GA. Internal runbook: api/docs/ops/iot-dogfood.md. Prefer SDK emits (OTLP protobuf) with setDeviceContext (SDK 0.1.8+).

Last updated

On this page