eemario commented on code in PR #27818: URL: https://github.com/apache/flink/pull/27818#discussion_r3049039255
########## docs/content/docs/deployment/advanced/historyserver.md: ########## @@ -97,6 +101,15 @@ Below is a list of available requests, with a sample JSON response. All requests Values in angle brackets are variables, for example `http://hostname:port/jobs/<jobid>/exceptions` will have to requested for example as `http://hostname:port/jobs/7684be6004e4e955c2a558a9bc463f65/exceptions`. +**Application-related requests** + + - `/applications/overview` + - `/applications/<applicationid>` + - `/applications/<applicationid>/jobmanager/config` Review Comment: You can indeed see all the jobs that were part of a completed application. The History Server's REST API is designed to mirror the standard JobManager REST API. This means that when you request an application's overview or details, the response naturally includes information about the jobs within it. To make this clear, I've added a note to the documentation explaining this behavior and have also included a link to the JobManager REST API page for reference on the response format. Thanks! -- 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]
