GitHub user Zhuoxi2000 added a comment to the discussion: [Discussion][Observability 1/2] Recording Agent Traces in the Event Log
Thanks for writing this up. the model reads well. One thing that might be worth mentioning explicitly is that the fields line up pretty closely with the OpenTelemetry GenAI semantic conventions. Since OTel export is listed as a non-goal here, I read that as a possible follow-up rather than a “never,” so calling out the alignment could make that future path clearer. Concretely: | This proposal | OTel GenAI | |---|---| | `input_run_id` | trace_id | | `execution_id` / `parent_execution_id` | span_id / parent_span_id | | `entity_type` + `entity_name` | `gen_ai.operation.name` + `gen_ai.tool.name` / `gen_ai.agent.name` | | `business_key` | `gen_ai.conversation.id` | | `status` / `problem_category` | span status + `error.type` | Two things might be worth deciding while the contracts are still open: 1. **ID shape.** OTel `trace_id` / `span_id` are fixed-width, 128-bit / 64-bit IDs. If these remain opaque strings, an exporter can hash them, but that hash needs to be stable across restarts and replays, so the ID derivation still matters. 2. **Run identity.** The doc says a run “creates or restores a run context,” but doesn’t define how `input_run_id` is derived. In #841, we seemed to converge on deriving it from stable runtime coordinates rather than `inputEvent.id`, since Java creates a fresh UUID when wrapping the event and that isn’t replay-stable. I think the same replay-stability concern applies here as well. Happy to take on the OTel export follow-up once this lands, if helpful. GitHub link: https://github.com/apache/flink-agents/discussions/900#discussioncomment-17670277 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
