wenjin272 opened a new issue, #1235: URL: https://github.com/apache/flink-agents/issues/1235
Parent: #1225 ### Problem and scope Metrics guidance starts with tables without sufficient scope/access context, then exposes detailed internal observation timing. Logging examples are asymmetric between Java and Python. #### Scope - [ ] Introduce the Flink Metrics system and link its metric types, reporters, and Web UI documentation rather than duplicating general definitions. - [ ] Move metric access instructions to the beginning and remove obsolete local-versus-Flink executor framing. - [ ] Explain the Scope column and how Agent, Action, Model Resource, Tool, Skill, MCP Server, and Subagent scopes map to paths and placeholders such as action_name/resource_name. - [ ] Keep stable metric meaning, scope, unit, and material boundaries. Remove unnecessary lifecycle observation ordering, fan-in, timeout/background-completion, and implementation-path narratives; place essential metric-specific qualifications next to the metric or in numbered notes. - [ ] Move version-specific metric migration details to migration/release notes. - [ ] Provide minimal Java/Python tabs for logging inside an Action and retain links to Flink logging documentation. #### Coordination and acceptance Can proceed independently of #1226; coordinate observability option references with #1234. Verify metric names/scopes/paths and logging examples against current code. Navigation, examples, and metric-specific qualifications must let a user find and interpret metrics without understanding internal scheduling. #### Review coverage DOC-057, DOC-058, DOC-059. These are traceability identifiers; the full actionable scope is described above. -- 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]
