> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vexa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tracing across flow, attempt, agent and tool

> Trace a Vexa dispatch across flow, attempt, agent and tool, and export those traces to your own observability stack.

**Can I trace a Vexa dispatch in my own observability stack?**

**Today:** No. Dispatch events stream on a per-dispatch topic, but there is no correlated trace across flow, attempt, agent and tool, and no export path.

**Sponsorable:** yes — The correlated trace and the export.

***

*Follow one piece of work across every hop, in your own observability stack.*

| | |
| - | - |
| **Status** | **sponsorable** |
| **Size** | M |
| **North star** | 4 · Agents that act on meetings, safely |
| **Measured by** | verified delegated authority and tracing |

## What it does

* Traces span flow, attempt, agent and tool.
* Exportable to the observability stack you already run.
* Makes a failure locatable rather than inferred.

## What exists today

Dispatch events stream on a per-dispatch topic, but there is no correlated trace across the four levels and no export path.

## What this adds

The correlated trace and the export.

## How sponsorship works

You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so "done" means done on your meetings. Your name goes on the release note. Sponsorship buys **the order of the queue** — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.

## Two doors

> [card] [Sponsor this](https://cal.com/dmitrygrankin/web?utm_source=docs\&utm_medium=roadmap\&utm_campaign=sponsor\&utm_content=tracing)
>
> Fifteen minutes. Bring the constraint you are under.

> [card] [Watch this](mailto:dmitry@vexa.ai?subject=Roadmap%20update%3A%20Tracing%20across%20flow%2C%20attempt%2C%20agent%20and%20tool\&body=watch)
>
> One email when it ships. The mail is already written — send it as it is.

## Questions

> [accordion] Can I trace a Vexa dispatch in my own observability stack?
>
> No. Dispatch events stream on a per-dispatch topic, but there is no correlated trace across flow, attempt, agent and tool, and no export path.

> [accordion] What would sponsoring this add?
>
> The correlated trace and the export.

> [accordion] What happens when it ships?
>
> It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.

***

*Ships upstream Apache-2.0 when sponsored.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.