wenjin272 opened a new issue, #1068: URL: https://github.com/apache/flink-agents/issues/1068
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description Flink Agents' Event Log records business Events, but it does not contain enough runtime context to reconstruct a single input run, distinguish concrete Action, LLM, Parser, and Tool executions, or attribute execution failures to the corresponding execution boundary. This issue tracks the Agent Trace recording capability designed in Discussion #900 and implemented by PR #924. The implementation extends the existing Event Log with: - run identity and business-key association; - execution identity and parent-child relationships; - lifecycle records for Action, LLM, Parser, and Tool executions; - stable execution outcomes and failure categories; - Java and Python alignment; - a normalized Event Log format that preserves business Event lineage; and - optional trace persistence controlled by `event-log.trace.enabled`. This scope covers recording only. Trace query APIs, visualization, OpenTelemetry export, evaluation datasets, and experiment tracking remain outside this issue. Related work: - Design discussion: #900 - Implementation PR: #924 - Original observability discussion: #710 - Business Event lineage: #841 and #923 ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
