oops reports contain 'scopedcollection:collectionresource' which is hard to debug/easy to ignore

e.g. in Lpnet Errors for 2010-07-15

=== Top 10 Time Out Counts by Page ID ===

    Hard / Soft Page ID
     142 / 139 ScopedCollection:CollectionResource

its very unclear that this is a (in this case) bugs/attachment API call. I am guessing, but I suspect errorlog.py isn't generating an appropriate pageid (and am also guessing that that would be a good place to fix it, as it keeps the complexity constrained to the generator, rather than the processor of the data - the generator knows the code that is actually executing, after all).

Fixing this would make OOPS reports that include such timeouts easier for domain teams to drill down into and fix.

Thanks,
Rob