Configure OTLP HTTP protobuf

Select your language guide to install its exporter and instrumentation. Configure OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf, the full OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://otlp.siteqwality.com/v1/traces and OTEL_EXPORTER_OTLP_TRACES_HEADERS=Authorization=YOUR_INGEST_KEY. A bare key avoids spaces in the environment header representation; Bearer is also accepted when correctly encoded by your SDK.

The generic OTEL_EXPORTER_OTLP_ENDPOINT is an origin to which SDKs append signal paths. Signal-specific endpoint variables are full URLs. Do not append /v1/traces twice or use /ingest for an OTLP envelope. Enable only exporters you actually configure. Logs need a logger bridge and metrics need instruments; setting an endpoint does not create data.

Allow batch processors to flush at shutdown, especially in scripts or serverless functions. Keep batches below wire/inflated limits. A 200 ExportResponse can contain partial-success rejections. Check exporter errors, then confirm the data in Traces. OTLP over gRPC is not available yet.