DanielLeens commented on issue #10588: URL: https://github.com/apache/seatunnel/issues/10588#issuecomment-5161279177
Thanks for picking this up and for keeping the first step documentation-focused. PR #11629 looks like the right initial slice for this issue: collect the relevant Zeta logs, isolate the job with `ST-JID`, preserve the first failure / exception chain, redact sensitive values, and cross-check any AI diagnosis against runtime metrics and the external system. Keeping support bundles, structured error extraction, and deeper tool integration as separate follow-up topics is also the right boundary. They are useful, but they should not block getting the first practical guide into the docs. Let's keep this issue tracked against #11629 for now. If that PR lands cleanly, we can close this docs issue and spin the larger runtime/tooling ideas into separate follow-up issues. -- 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]
