Bug 12332

Summary: Regularly purge the error report database
Product: [Yocto Project Subprojects] Error Reporting tool Reporter: Paul Eggleton <bluelightning>
Component: Error Reporting ToolAssignee: Michael Halstead <mhalstead>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: amanda.r.brindle, mhalstead, randy.macleod, stephano
Version: unspecified   
Target Milestone: 2.7 M1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Paul Eggleton 2017-11-10 04:01:18 UTC 
The error report database has grown to a huge size, and this is significantly affecting the performance of the application. We need to purge the database on a regular basis to get rid of old reports that we don't need.

About the only complication I can think of is that reports may be linked from bugzilla and those may need to stay around for longer. We could potentially have the application look at the referrer and make the entry "sticky" if it's bugzilla, that's probably the easiest way to deal with it.
Comment 1 Michael Halstead 2018-09-14 19:49:59 UTC 
Purge is running from cron every day now. We are keeping 180 days back plus any viewed reports. We will reduce to 30 day retention over time.