[Feat]: EventQueue should propagate trace context? #281
Description
Is your feature request related to a problem? Please describe.
a2a Python SDK 0.2.10
The A2A Python SDK integrates OpenTelemetry tracing via its utility library, and key classes/functions are instrumented for observability. However, the trace context is not propagated across the EventQueue. When using message_stream, the trace_id changes between enqueue_event and dequeue_event, resulting in fragmented and incomplete trace information for asynchronous processes.
Describe the solution you'd like
Maybe the SDK should propagate and maintain the trace context across asynchronous boundaries like the EventQueue, ensuring that the same trace_id is used from event enqueue to dequeue. This would allow for end-to-end trace continuity and more accurate distributed tracing in asynchronous workflows.
Describe alternatives you've considered
not yet
Additional context
No response
Code of Conduct
- I agree to follow this project's Code of Conduct