Feature #16162

Custom time for report expiration

Added by Ondřej Pražák 7 months ago. Updated 6 months ago.

Status:New
Priority:Normal
Assigned To:-
Category:Reporting
Target version:Team Marek backlog
Difficulty: Bugzilla link:1359491
Found in release: Pull request:
Story points-
Velocity based estimate-

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1359491
Proposed title of this feature request
- [RFE] Custom time for report expiration

What is the nature and description of the request? 
- /etc/cron.d/foreman includes a cron job to expire
foreman reports. User would like to configure these
settings to suit their organization's needs rather than
use the provided defaults. User is not interested in
reports where nothing happened. Those could be expired
after just a few days. We do, however, want to keep
active reports for much longer than a week. User wants the defaults as an option under the Settings menu. It should feature options for inactive reports and active reports.
How would the user like to achieve this? (List the functional requirements here) 
- By adding feature options for inactive reports and active reports.

History

#1 Updated by Ondřej Pražák 7 months ago

  • Subject changed from Custom time for report expiration to Custom time for report expiration
  • Category changed from Trends to Reporting
  • Target version set to Team Marek backlog

#2 Updated by Marek Hulán 7 months ago

I'm not sure whether Foreman application running under foreman user should touch files in /etc/cron.d normally owned by root. We could either use foreman's crontab or use foreman-tasks scheduler. I prefer staying with cron. Anyway since it's currently hard coded in https://github.com/theforeman/foreman-packaging/blob/rpm/develop/foreman/foreman.cron.d:"foreman package" I agree that it would be better to make this configurable.

#3 Updated by Ondřej Pražák 6 months ago

Additional info from user: there should be an option to always preserve the most recent report.

Also available in: Atom PDF