Skip to main content
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.

​
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

Sponsor this

Fifteen minutes. Bring the constraint you are under.

Watch this

One email when it ships. The mail is already written — send it as it is.

​
Questions

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.
The correlated trace and the export.
It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
Ships upstream Apache-2.0 when sponsored.