IoT edge gatewayCopy Anchor Link

Site gateways and industrial edge nodes typically run an OpenTelemetry Collector (or the Owlpane agent chart) that forwards device logs to Owlpane ingest with a project owl_ing_* key.

This is not the same as Agent samples in the console (Kubernetes node metrics from the in-cluster agent).

Attributes on every log recordCopy Anchor Link

• owlpane.device.id — matches Device fleets inventory deviceId
• owlpane.device_fleet.id — fleet slug from Owlpane
• Optional: owlpane.device.class, owlpane.device.firmware_version, owlpane.device.gateway_id

Ingest 0.1.1+ also accepts aliases device.id, fleet.id, and device.fleet.id and normalizes them at the gateway.

Collector exampleCopy Anchor Link

processors:
  resource/device:
    attributes:
      - action: upsert
        key: owlpane.gateway.id
        value: ${env:HOSTNAME}

exporters:
  otlphttp/owlpane:
    endpoint: ${env:OWLPANE_INGEST_URL}
    headers:
      Authorization: "Bearer ${env:OWLPANE_INGEST_KEY}"

SDK at the deviceCopy Anchor Link

When the device runs an Owlpane SDK, prefer helpers instead of hand-rolling attribute names:

• Node — setDeviceContext + emitDeviceLog (@owlpane/node 0.1.7+)
• Python — set_device_context / device_log_attributes (0.1.8+)
• Go / Java — SetDeviceContext / DeviceAttributes.build

See IoT telemetry contract.

HelmCopy Anchor Link

Use the standard agent Helm chart for collector deployment; chart 0.3.7+ documents IoT env patterns in the Owlpane agent repo (docs/iot-edge-gateway.md).