Traces (OTLP)

Endpoint POST /v1/traces

OpenTelemetry SDKs and Collectors export spans here, and the Blipit SDKs send their spans here too.

1Request

X-Blipit-Key or Authorization: Bearer, public or secret. OTLP/HTTP JSON body up to 4 MB, gzip, deflate or brotli accepted, at most 1,000 spans per request. service.name from the resource names the service; server and consumer spans and roots become transactions. Descriptions are cut at 1,000 characters (db statements 2,000); 32 tags of 256 characters each are kept.

ini
OTEL_EXPORTER_OTLP_ENDPOINT=https://in.blipit.io
OTEL_EXPORTER_OTLP_PROTOCOL=http/json
OTEL_EXPORTER_OTLP_HEADERS=x-blipit-key=<public key>
OTEL_SERVICE_NAME=shop-api

2Responses

200 {accepted: true, spans: n}. 202 {accepted: false, reason: 'monthly span allowance used up'}. 400 unreadable JSON. 413 more than 1,000 spans. 415 protobuf content type. 401 unknown key.

Good to know

  • Spans per month: Free 1M, Solo 2M, Team 10M, Scale 20M; kept 7 days on Free and Solo, 14 on Team and Scale.
  • gRPC and protobuf are not read; keep the protocol on http/json.
  • 409 when the data comes from a different platform than the project's, for example {"error": "This project is for iOS. Create a separate Android project in Blipit and use its key.", "reason": "platform_mismatch", "project_platform": "ios", "sent_platform": "android"}. Events, sessions, logs, OTLP traces and metrics, bug reports, replays and web vitals all answer this way. Refused data is not stored and does not count against the quota. The Blipit SDKs log this error once and stop sending for the rest of the run. To fix it, create a project for that platform and use its key.

Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.