This PR adds a persistent file-based job log. The log store is configured with a TTL which specified how many days (at a minimum) to keep log files for. Currently there is no automatical log pruning, but there is a method which we could hook into an admin interface or tie to a timer if we want at a later date.
When a log is stored the log store generates a log id (actually a relative path from the base directory), which is then stored in the ES JobInfo record. This can be used in an API call to api/logs to get the actual log content.
Right now the logs are not integrated into the UI.
This PR adds a persistent file-based job log. The log store is configured with a TTL which specified how many days (at a minimum) to keep log files for. Currently there is no automatical log pruning, but there is a method which we could hook into an admin interface or tie to a timer if we want at a later date.
When a log is stored the log store generates a log id (actually a relative path from the base directory), which is then stored in the ES JobInfo record. This can be used in an API call to api/logs to get the actual log content.
Right now the logs are not integrated into the UI.