Bug 12332 - Regularly purge the error report database
Summary: Regularly purge the error report database
Status: RESOLVED FIXED
Alias: None
Product: Error Reporting tool
Classification: Yocto Project Subprojects
Component: Error Reporting Tool (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.7 M1
Assignee: Michael Halstead
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-11-10 04:01 UTC by Paul Eggleton
Modified: 2018-09-14 19:49 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.