autonomy telemetry bridge

Start an OTLP/HTTP → control-plane event bridge

Synopsis

Starts an HTTP server that accepts OTLP/HTTP log payloads (POST /v1/logs)
from an OTel Collector and converts them into control-plane events, then
forwards the batch to the control-plane POST /v1/events endpoint.

Conversion rules:
  kind="decision"  → event_type="ai.policy.decision"
  kind="action"    → event_type="ai.agent.action"
  kind="lifecycle" → event_type="ai.agent.lifecycle"
  kind="error"     → event_type="ai.agent.error"
  other            → event_type="ai.telemetry.<kind>"

  event_id  = "<service.name>:wal:<seq>"  (stable per WAL entry)
  node_id   = resource attribute service.name
  timestamp = log record timeUnixNano converted to RFC3339

Network errors forwarding to --forward-url are logged but do not fail the
OTLP response, so the upstream collector will not retry indefinitely.

Usage

autonomy telemetry bridge [flags]

Options

      --forward-url string   Control-plane events endpoint, e.g. http://localhost:8888/v1/events (required)
      --listen string        TCP address to listen on for incoming OTLP/HTTP (default "127.0.0.1:4318")

Options inherited from parent commands

      --require-signed-manifest   Refuse to start if the SHA256SUMS release manifest or its cosign signature is missing/invalid (Tier 2 binary-integrity check; default: build-time compile-in via -ldflags -X, build-hardened artifacts=true, all others=false)

See also