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

Feature #7234

Report history should be configurable.

Added by Jason Rojas over 3 years ago. Updated almost 3 years ago.

Status:ClosedStart date:04/25/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

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

Description

With one of my small 400 node environments, the reports table grows to 300k+ reports in close to 7 days. I have had to disable reporting for all of my environments with more than 1000 nodes due to performance issues but this seems to be problematic. It would be nice to add configuration options for how many successful and/or failed reports per-node to keep. I wrote a rake task to to run through all nodes and delete any reports over a specified limit but it runs just as fast as reports come in.


Related issues

Related to Puppet Dashboard - Feature #7344: End-user control over automated database cleanup. Accepted 05/03/2011
Related to Puppet Dashboard - Feature #6717: Cleanup of table resource_statuses in dashboard-database Closed 03/15/2011

History

#1 Updated by James Turnbull over 3 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Nigel Kersten

#2 Updated by Nigel Kersten over 3 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)

#3 Updated by Nigel Kersten almost 3 years ago

  • Status changed from Accepted to Closed

Since this ticket we’ve improved the rake prune task with Dashboard to let you configure thresholds for pruning, and a cron job to use that is the suggested path forward.

Ultimately we’ll end up moving to building a ReportService that Dashboard talks to, rather than Dashboard owning the report storage, and this will ultimately be configurable there.

Also available in: Atom PDF