davidzollo opened a new issue, #10636: URL: https://github.com/apache/seatunnel/issues/10636
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues) and found no similar issues. ### What happened After upgrading to SeaTunnel 2.3.13, the Zeta Web UI job detail page renders task metrics as `NaN` in the Overview table. This happens even when the frontend and backend are upgraded together to the same version. ### Reproduce 1. Start Zeta with a 2.3.13 backend. 2. Open a running job in the Web UI detail page. 3. Check the Overview table metrics such as `Received Count`, `Write Count`, `Received QPS`, `Write QPS`, etc. 4. The values render as `NaN`. ### Root cause `2.3.13` backend changed table metric keys from raw table paths like `fake.user_table` to vertex-prefixed keys like `Source[0].fake.user_table` / `Sink[1].fake.user_table` when building detail metrics. But the UI detail page still looks up metrics by raw `row.tablePaths` and does `Number(job.metrics[key][path])`. When the raw key is missing, the lookup returns `undefined`, so the UI renders `NaN`. So this is not a mixed-version deployment issue. It is a release-internal contract mismatch between the 2.3.13 backend response and the detail page lookup logic. ### Expected The UI should correctly read vertex-prefixed metric keys returned by the 2.3.13 backend and keep backward compatibility with raw table-path keys. ### Additional context The regression appears related to the job metrics refactor in `#10273`. -- 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]
