DanielLeens commented on issue #11352: URL: https://github.com/apache/seatunnel/issues/11352#issuecomment-4888298530
This looks like a worthwhile enhancement, but it needs a slightly sharper design boundary before implementation. The user problem is clear: today we expose pieces of backpressure data, but we still do not give operators a direct “what is the bottleneck right now, and is it transient or chronic?” workflow. The main design questions I would want clarified first are: 1. what time window the blocked/queue signals represent 2. how ranking should work when multiple edges are simultaneously pressured 3. how this page reuses the existing runtime metrics model instead of inventing a separate one 4. what the fallback is for larger DAGs where too much live detail becomes noisy A strong V1 would probably focus on ranking the worst edges/vertices, showing short-window trends, and linking back into the existing detailed metrics/log views. That keeps the feature actionable without making the first version too broad. -- 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]
