OpenTelemetry API
Use the OpenTelemetry API to send OTLP/HTTP protobuf traces and logs to Altertable. Altertable writes accepted telemetry into the managed opentelemetry catalog for the target environment.
For application setup, prefer the standard OpenTelemetry SDKs. This page documents the HTTP endpoints those SDKs and collectors send to.
Connection details
Hostname | Port | Protocol |
|---|---|---|
api.altertable.ai | 443 (HTTPS) | OTLP/HTTP protobuf |
Authentication
Authenticate requests with the same HTTP Basic Auth credentials used by the Lakehouse API. Base64-encode your credentials in the format lakehouse_username:lakehouse_password:
echo -n "your_lakehouse_username:your_lakehouse_password" | base64
Then send the encoded value in the Authorization header:
Authorization: Basic <ALTERTABLE_BASIC_AUTH_TOKEN>
Endpoints
Signal | Endpoint | Request body | Content type |
|---|---|---|---|
Traces | POST https://api.altertable.ai/v1/traces | OTLP ExportTraceServiceRequest protobuf payload | application/x-protobuf |
Logs | POST https://api.altertable.ai/v1/logs | OTLP ExportLogsServiceRequest protobuf payload | application/x-protobuf |
Altertable does not support OpenTelemetry metrics yet. Do not send OTLP metrics payloads to Altertable.
POST /v1/traces
Send OTLP trace data:
curl https://api.altertable.ai/v1/traces \-H "Authorization: Basic $ALTERTABLE_BASIC_AUTH_TOKEN" \-H "Content-Type: application/x-protobuf" \--data-binary @traces.pb
Accepted spans are written to opentelemetry.main.spans.
POST /v1/logs
Send OTLP log data:
curl https://api.altertable.ai/v1/logs \-H "Authorization: Basic $ALTERTABLE_BASIC_AUTH_TOKEN" \-H "Content-Type: application/x-protobuf" \--data-binary @logs.pb
Accepted log records are written to opentelemetry.main.logs.
Related docs
- OpenTelemetry ingest: enable the catalog and configure SDKs or collectors.
- OpenTelemetry OTLP specification: request payload definitions and protocol behavior.
- Lakehouse API authentication: Basic Auth format for lakehouse credentials.