danielnadean commented on issue #11665:
URL: https://github.com/apache/seatunnel/issues/11665#issuecomment-5235177831

   I would like to work on this issue.
   
   I will start with the STIP/design required above, focused on:
   - how per-worker slot total/used will be derived and kept consistent with 
the live scheduler view (the one genuinely new piece of state here)
   - whether `/trace/task-mapping` is sufficient as-is for the per-worker 
"tasks running here" drill-down, or needs a narrower read path
   - refresh interval/cost once the page renders the full 
`/system-monitoring-information` payload instead of today's 4 fields
   
   I'll open the STIP/design PR first and continue with implementation after 
maintainer alignment, following the same sequencing used on #11351.
   


-- 
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]

Reply via email to