Hi Elias, in theory, it could be integrated into a single web interface, but this was not done so far. I guess the main reason for keeping it separate was probably to have a better separation of concerns as the history server is actually independent of the current JobManager execution and merely displays previous job results which may also come from different or previously existing JobManager instances which stored history data in its storage directory.
Chesnay (cc'd) may elaborate a bit more in case you'd like to change that and integrate the history server (interface) into the JobManager. Nico On Sunday, 24 September 2017 02:48:40 CEST Elias Levy wrote: > I am curious, why is the History Server a separate process and Web UI > instead of being part of the Web Dashboard within the Job Manager?
