SEZ9 commented on issue #11662: URL: https://github.com/apache/seatunnel/issues/11662#issuecomment-5215602751
Confirmed against dev: LogService builds log URLs from member.getAddress().getHost() (or the systemMonitoring 'host' field) plus the node HTTP port, with no config to override the advertised host. This breaks any deployment where the browser cannot reach member IPs directly (Ingress, NAT, reverse proxy). Of the two proposed fixes, adding a `seatunnel.engine.http.public-url` (or `public-host`/`public-scheme`) option seems necessary for the multi-node case, since /logs aggregates files from different members and a purely relative link would only resolve against the node serving the request. Relative links alone would only be correct in single-node or shared-storage setups. Would you be willing to submit a PR? A reasonable approach: use the configured public URL when set, otherwise fall back to the current member-address behavior, keeping backward compatibility. Please also cover the HTML output of /logs and the Web UI job log list in tests. <!-- streview-comment:68 --> -- 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]
