githubEdit

magnifying-glass-chartZipkin

Distributed tracing with Zipkin

Spice supports distributed tracing by integrating with Zipkin and compatible tracing systems. Traces capture completed tasks — SQL queries, AI chat completions, tool calls, dataset refreshes — recording execution time, inputs, outputs, and errors.

Configuration

Enable Zipkin tracing by configuring the runtime.tracing section in your app's spicepod.yaml:

runtime:
  tracing:
    zipkin_enabled: true
    zipkin_endpoint: "http://your_zipkin_host:9411/api/v2/spans"
Parameter
Default
Description

zipkin_enabled

false

Enables or disables Zipkin trace export.

zipkin_endpoint

Required if enabled. The /api/v2/spans endpoint on your Zipkin instance.

Trace data will be available in the Zipkin UI at http://your_zipkin_host:9411. See the Zipkin Quickstartarrow-up-right to run a test server.

Trace Information

A trace in Spice represents a completed task. Each trace is a unique span recording execution time, inputs, outputs, and errors.

Field
Description

trace_id

Unique identifier for the trace

span_id

Unique identifier for the span

task

Task type (e.g. sql_query, text_embed, health)

start_time

When the task started

end_time

When the task completed

execution_duration_ms

Execution duration in milliseconds

error_message

Error details, if the task failed

Example trace data:

For more details, see Task History.

See also:

Last updated

Was this helpful?