Traces

Send OpenTelemetry traces to Altertable when you want spans, service timing, status, attributes, events, and links to be queryable beside product, operational, and business data.

Accepted spans are written to opentelemetry.main.spans.

Endpoint

Send OTLP/HTTP protobuf traces to:

POST https://api.altertable.ai/v1/traces
Copy

Use Content-Type: application/x-protobuf and authenticate with the same HTTP Basic Auth credentials used by the Lakehouse API.

Copy
1
2
3
4
curl https://api.altertable.ai/v1/traces \
  -H "Authorization: Basic $ALTERTABLE_BASIC_AUTH_TOKEN" \
  -H "Content-Type: application/x-protobuf" \
  --data-binary @traces.pb

SDK and collector setup

Use the standard OpenTelemetry SDK for your application language and configure its OTLP/HTTP exporter to send traces to Altertable. The SDK handles instrumentation, batching, resource attributes, and protobuf encoding.

See the OpenTelemetry SDK documentation for language-specific setup guides.

Query traces

Spans are normal SQL rows once they are ingested:

Copy
1
2
3
4
5
6
7
8
9
10
11
SELECT
  trace_id,
  span_id,
  service_name,
  name,
  start_time,
  duration_ms,
  status_code
FROM opentelemetry.main.spans
ORDER BY start_time DESC
LIMIT 100;

You can also explore traces in the Altertable Explore tab with Lucene-syntax search.