We are experiencing problems because developers from time to time enable very extensive logging (sometimes many GBytes of size) and than publish the log file to main QB server. On the server we can see sudden impact on data storage, but it's hard to identify which configuration is causing the problem.

It would be very helpful to have the total size of published artifacts as an attribute of a build, which could be accessed via REST api.