Telemetry endpoint

Boidra Platform exposes an OpenTelemetry-compatible ingest endpoint. Point any OTLP/HTTP exporter at it.

Ingest

POST /otel/v1/traces
POST /v1/traces            (equivalent — both are accepted)

• Protocol: OTLP over HTTP.
• Content-Type: application/json (OTLP/JSON) or application/x-protobuf (OTLP protobuf). Both are parsed.
• Body: a standard OTLP ExportTraceServiceRequest (resourceSpans[…]).
• Response: 200 OK with { "partialSuccess": {} } on success.

Exporter configuration

Set the endpoint so your SDK posts under /otel:

export OTEL_EXPORTER_OTLP_ENDPOINT="https://<your-dashboard-host>/otel"

The OpenTelemetry SDK appends /v1/traces automatically. If your SDK defaults to gRPC (the SAP Cloud SDK for Python does), also set:

export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"

What happens to a span

1. The payload is parsed (JSON or protobuf).
2. Each span is classified and mapped per the OTLP attributes reference.
3. Non-GenAI / wrapper spans are skipped; the rest are stored.
4. The dashboard reads stored spans through the Dashboard API.

CORS & ports

• The backend runs on port 3010 by default (PORT to override).
• CORS is permissive (*) so browsers and remote agents can post directly.

Health

GET /health   →   200 { "status": "ok" }

Use it for readiness checks.