tracing
tracing overrides the global [trace_storage] policy for one channel. Each field is independently optional; an unset field falls back to the global value.
Synopsis
{
"tracing": { "mode": "async", "errors_only": true, "task_details": true }
}
Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
mode | string | no | global trace_storage.mode | sync, async, batch, or off. |
sample_rate | number | no | global trace_storage.sample_rate | Fraction of traces persisted, 0.0–1.0. Applies to sync traces only; async traces always persist. |
errors_only | boolean | no | global trace_storage.errors_only | Persist only traces that ended with errors. |
task_details | boolean | no | false | Capture a per-task execution trace into task_trace_json. No global setting exists — this is per-channel only. |
Note
Each
task_detailstrace grows with message size times task count. Enable it for debugging, not as a default. The recorded shape is specified under the trace object.
Related
- Trace persistence settings: the global policy this overrides.
- Traces and async processing: choosing a mode.
- Data API › The trace object: the recorded shape of
task_details. - Channel configuration: every key, with its page.
Last verified 14 September 2026