OpenTelemetry — `otlp`

Receives OTLP/HTTP logs, traces, and metrics at POST /v1/{logs,traces,metrics}. One source ingests every service: resource attributes (e.g. service.name) become labels, so everything an OTel SDK or Collector exports correlates by service with no per-service setup.

Prerequisites: something exporting OTLP — an instrumented app or an OpenTelemetry Collector, pointed at the daemon. For OTLP/gRPC, the otlp-grpc extra (pip install 'navflow[otlp-grpc]'); the receiver listens on :4317 (NAVFLOW_OTLP_GRPC_PORT, off to disable).

Set up

Agent

Ask a connected agent:

Use navflow to create an OTLP source keyed by service.

The agent calls create_source; then point your exporter at the daemon (below).

Console

Sources → Add source → otlp. There is no required config; the service label (from service.name) is the natural key. Save.

YAML / API


- name: otel
  connector: otlp
  config:
    labels:
      - { name: service, field: service, primary: true }

Or POST /api/sources with the same object.

Then point the exporter at the daemon:


OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:8787   # OTLP/HTTP → /v1/{logs,traces,metrics}
# or gRPC (otlp-grpc extra): OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4317

If NAVFLOW_INGEST_TOKEN is set, exporters must send it (Authorization: Bearer or X-NavFlow-Token).

Configuration

No connector-specific fields — just labels. Resource attributes are available as label fields (service from service.name).

Verify

Recent events shows spans/logs/metric points as they arrive; Explore lists services under the service key.

OpenTelemetry — otlp