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 #7344

End-user control over automated database cleanup.

Added by Nigel Kersten over 4 years ago. Updated almost 4 years ago.

Status:AcceptedStart date:05/03/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

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

Description

People collect a lot of data about their nodes in Dashboard.

Different people have different requirements for preserving historical data, and we need to give them control over automated cleanups.

Some people may wish to do this on a per-host basis, some on a per-time basis. We should ship appropriate rake tasks for all this functionality and offer the ability to create cron jobs to run these tasks.


Related issues

Related to Puppet Dashboard - Feature #6717: Cleanup of table resource_statuses in dashboard-database Closed 03/15/2011
Related to Puppet Dashboard - Feature #7234: Report history should be configurable. Closed 04/25/2011
Related to Puppet Dashboard - Bug #6828: Dashboard takes too long to remove a node Closed 03/24/2011

Also available in: Atom PDF