DanielLeens commented on issue #11352: URL: https://github.com/apache/seatunnel/issues/11352#issuecomment-5395007751
Thanks for following up. Yes, this issue is still available. Because this feature touches UI behavior, runtime metrics semantics, and larger-DAG observability, please start with a focused STIP/design note before moving into implementation code. The most important V1 boundaries to pin down are: 1. what time window the blocked/queue signals represent; 2. how the page ranks multiple simultaneously pressured edges or vertices; 3. how it reuses the existing runtime metrics model and endpoints instead of inventing a separate data path; 4. what the fallback is for larger DAGs where too much live detail becomes noisy. A good first slice would be: identify the worst bottleneck candidates, show short-window trend context, and link back into the current detailed metrics/log views. Once you have the design doc, please link it here so maintainers can review the boundary before code starts. -- 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]
