DanielLeens commented on issue #11665: URL: https://github.com/apache/seatunnel/issues/11665#issuecomment-5229110041
This looks like a reasonable infrastructure-observability feature request rather than a runtime bug. The proposal is also scoped in a good way: most of the data is already available, and the one genuinely new contract appears to be per-worker slot accounting. That distinction matters, because surfacing existing monitoring fields is mostly a UI/read-path problem, while per-worker slot totals and usage become scheduler-facing correctness data. From a review perspective, the most important design questions are: 1. how per-worker slot total/used will be derived and kept consistent with the live scheduler view; 2. whether `/trace/task-mapping` is already sufficient for the "what is running on this worker" drill-down, or needs a narrower server-side read path; 3. what refresh cost is acceptable on larger clusters once the page renders more of the monitoring payload continuously. So I would keep this open as a dedicated feature, with the implementation split kept narrow: first make the contract around per-worker slots explicit, then wire the existing monitoring/task-mapping data into the UI around that contract. -- 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]
