In https://jira.mongodb.org/browse/EVG-12398 I reported an example of a log file which was not downloadable via API. The following suggestion was given:
> just downloaded your logs using the evergreen cli, they are too large for the UI to download. The task logs alone are 3.2G, at these sizes the UI can't handle downloading and displaying the logs. I would suggest trying to make the logs smaller, and for larger logs in general, use the `evergreen buildlogger fetch` command on the command line.
As an API user of Evergreen, I would like to be able to detect this condition via API.
- In the resource(s) referencing logs, include the log size.
- In the resource for downloading the log file itself, produce a descriptive error if the log file exceeds a certain threshold (i.e. do not just close connection after 1 minute of sending data).
- Provide an additional endpoint for determining the size of a particular log file.