GitHub user joeyutong added a comment to the discussion: [Discussion][Observability 1/2] Recording Agent Traces in the Event Log
Thanks for pointing this out and for offering to help. I agree that OpenTelemetry export should be a supported follow-up, and I believe the proposed recording model provides the information needed to implement it: an input run defines the Trace boundary, the execution hierarchy provides the Span topology, and lifecycle Events provide execution timing and outcomes. The exact GenAI attribute mapping can be worked out as part of the exporter design. For ID shape, I would prefer to keep the framework IDs opaque rather than constrain them to the OTel representation. An exporter can derive valid fixed-width Trace and Span IDs from the native identities. The current `input_run_id` represents one runtime processing instance. It is preserved when an existing `ActionTask` is restored from Flink state, while a source-replayed input creates a new run and would therefore produce a new OTel Trace. I have not yet identified a Trace or OTel export requirement that requires the ID to remain stable across source replay; a concrete use case would help determine whether that semantic should change. An OTel exporter follow-up would be very welcome once the recording contract is settled. GitHub link: https://github.com/apache/flink-agents/discussions/900#discussioncomment-17697343 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
