This switches the output from something like this:
blocked: 0 broken: 6 brokendeps: 0 common: 1125 grey: 0 ignore: 10 missing: 5 noroot: 0 pending: 4 total: 1150
broken: 6 (+0 replaced)
cjdns-17.3-12.fc24 firefox-45.0.2-2.fc24 swig-3.0.8-6.fc24 i7z-0.27.2-16.20150629gitec09c4f.fc24 bes-3.17.0-3.fc24 kubernetes-1.2.0-0.18.git4a3f9c5.fc24
noroot: 0 (+0 replaced)
blocked: 0 (+0 replaced)

to a list of failed builds sorted by the number of packages that this failure blocks:
-- top broken packages --
sbcl-1.1.18-1.fc21 (23)
thunderbird-38.6.0-6.fc24 (20)
firefox-45.0-4.fc24 (20)
nunit-2.6.4-11.fc24 (18)
mlton-20100608-16.fc20 (10)
gap-4.8.3-1.fc24 (9)
ocaml-ocamlnet-4.0.4-3.fc24 (7)
coq-8.5-1.fc24 (7)
ldc-0.16.1-77.fc24 (6)
ghc-gtk-0.13.9-3.fc24 (6)
qt5-qtwebengine-5.6.0-0.19.rc.fc24 (5)
gtk2hs-buildtools-0.13.0.5-1.fc24 (5)
ghc-pandoc-types-1.16.1-1.fc24 (5)
OCE-0.16.1-6.fc24.1 (5)
shim-0.8-1.fc22 (4)
polymake-2.14r1-4.fc24 (4)
pocl-0.12-1.fc24 (4)
perl-Perlbal-XS-HTTPHeaders-0.20-17.fc23 (4)
nacl-binutils-2.24-8.git1d8592c.fc24 (4)

The number behind the package is the number of blocked packages.
This new output allows us to prioritize our work so that the most blocking packages get fixed first.

@sharkcz - you asked for this to be split off from the logfile patch. Did you have concerns about this?