GitHub user Zhuoxi2000 added a comment to the discussion: [Discussion][Observability 1/2] Recording Agent Traces in the Event Log
Thanks! The checkpoint-aligned run identity plus `status="reused"` for replayed actions resolves my replay-stability concern. I also agree that keeping Execution Events out of Action routing is the right call, and `event-log.trace.enabled` defaulting to off makes sense given the log-volume concern @weiqingy raised. Since this covers trace recording, I’d be happy to pick up the export side as a follow-up: mapping Execution Events to the OpenTelemetry GenAI semantic conventions, including `invoke_agent` / `execute_tool` / `chat` spans and `gen_ai.usage.*` token attributes, gated behind config in the same way. I’ve implemented the inverse mapping, OTel GenAI to storage, in a side project, so I have a concrete attribute table to start from. Happy to open a `[DISCUSS]` with the full mapping if that would be useful for Observability 2/2. GitHub link: https://github.com/apache/flink-agents/discussions/900#discussioncomment-17738901 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
