412790 - add a way to tell clients to stop sending reports for a particular version or build id

Status: RESOLVED WONTFIX

(Socorro :: Backend, task, P3)

Description

[(not currently active) Ted Mielczarek]

See bug 412788.  Not a huge priority on the server side, since we're not end-of-lifing anything anytime soon, but we should eventually figure out how to do this.  Since it will have to be in the collector, it should be fast and not rely on the db.  One thought I had was having a db table for end-of-lifed products, and then just a cron job or something that turned that into a python file that the collector could read.  It doesn't have to be generated in realtime, but having it in the db would make maintenance a lot easier.

Comment 1

[K Lars Lohn [:lars] [:klohn]]

This is resolved by the server side throttling enhancement.  A filter can be added to the collector configuration file to simply block a particular version of a product.

Comment 2

[(not currently active) Ted Mielczarek]

No, that's not what this asks for. bug 412788 implemented a feature in the client (which shipped with Firefox 3.0, even) where if the collector replies with
"StopSendingReportsFor=VERSION"
the client will not even attempt to submit reports for that version any longer.

Comment 3

[Michael Morgan [:morgamic]]

Ballpark = January.  Collector would have to be modified to send a response field based on version.

Comment 4

[Laura Thomson :laura]

Simple change, revisit soon

Comment 5

[Laura Thomson :laura]

Ted: any interest in still doing this?

Comment 6

[(not currently active) Ted Mielczarek]

I guess it's probably not super important. We can always just throttle down processing on old versions. We've got at least two major versions that are no longer supported: 3.0 and 3.5. What volume of crashes are we still getting from them?

Comment 7

[Robert Kaiser]

I'd think we don't really need to do this - unless we find out those reports from old versions are causing us any trouble.

BTW, seeing some reports from old versions around at times makes us realize how far back (version-wise) a signature has been around and so can make us determine it can't be a recent regression.

Comment 8

[(not currently active) Ted Mielczarek]

I'd definitely take Socorro/CrashKill's decision on this over mine, it doesn't affect me at all. I just added this capability because apparently the old crash reporting system had something similar, and we thought we might need it.

Comment 9

[Laura Thomson :laura]

Kairo thinks we don't need it - I'm good with that.