The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Feature #4824

Different kinds of reports should be purged on different schedules

Added by Igal Koshevoy almost 5 years ago. Updated over 4 years ago.

Status:AcceptedStart date:09/22/2010
Priority:LowDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Keywords: Affected URL:
Branch: Affected Dashboard version:

Description

Currently the rake task for purging old reports just uses the report’s timestamp to determine if it should be purged. However, in #2976 “Remove reports”, a user requested the following feature:

Martin Englund wrote: There should be a setting to purge “ok” reports quicker and “failed” or “changed” slower – you typically want the ones with changes to stick around for a couple of weeks.


Related issues

Related to Puppet Dashboard - Feature #2976: Remove reports Closed 12/23/2009

History

#1 Updated by Anonymous almost 5 years ago

  • Target version set to 1.1.0

#2 Updated by James Turnbull over 4 years ago

  • Target version deleted (1.1.0)

#3 Updated by Anonymous over 4 years ago

  • Status changed from Needs Decision to Accepted
  • Priority changed from Normal to Low

Also available in: Atom PDF