Skip to content

Execution trace correlation across workflows #5

@JaimeStill

Description

@JaimeStill

Migrated from tailored-agentic-units/tau-orchestrate#1

Summary

Correlate events across workflow boundaries so that a single execution can be traced end-to-end, even when workflows compose (e.g., a state graph node that runs a parallel workflow internally).

Requirements

  • Assign a trace ID at the top-level execution entry point
  • Propagate trace ID through nested workflow invocations via context
  • Include trace ID in all emitted events
  • Enable reconstruction of full execution timeline from collected events

Design Constraints

  • Backward compatible: existing Observer interface must not change; new capabilities extend through new observer implementations or optional interface methods
  • Zero-overhead default: NoOpObserver behavior must remain zero-cost; advanced features are opt-in
  • Registry compatible: new observers must integrate with the existing string-based registry pattern
  • Event model stability: existing Event structure and EventType constants are the contract; new event types can be added, existing ones should not change semantics

Acceptance Criteria

  • Trace correlation enables end-to-end reconstruction of composed workflow execution
  • All new observer implementations pass through the existing registry pattern
  • No performance regression for existing NoOpObserver and SlogObserver usage

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew functionalityorchestrateorchestrate subsystem

    Type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions