Bug #5334
closed
The archiving logic of execution reports needs to be adapted for "error only" report mode
Added by Nicolas CHARLES over 10 years ago.
Updated almost 10 years ago.
Category:
Web - Compliance & node report
Description
We are currently archiving reports based on date. However, in report_only mode, this may not make sense, if executions are not often enough. We should at least enforce that we have several execution kept in store.
- Subject changed from Change the archiving logic in "report_only" mode to Change the archiving logic in "error only" report mode
- Subject changed from Change the archiving logic in "error only" report mode to Change the archiving logic of execution reports in "error only" report mode
- Target version changed from 140 to 3.0.0~beta1
- Tracker changed from Enhancement to Bug
- Subject changed from Change the archiving logic of execution reports in "error only" report mode to The archiving logic of execution reports needs to be adapted for "error only" report mode
- Target version changed from 3.0.0~beta1 to 3.0.0~beta2
Since this new mode was implemented in #5293, but this was released in 3.0.0~beta1, and not addressed.
- Parent task deleted (
#5293)
- Target version changed from 3.0.0~beta2 to Ideas (not version specific)
I'm not sure anymore of the the rationnal for that, because:
- we have at least one report batch sent by day (inventory + hearbeat at min one by day)
- archiving can't occure more often than every day.
So for now, I propose to post-pone that until someone is able to explain why it should be so.
- Status changed from New to Rejected
well, actually closing it because it makes no sense until we keep the curren timplemented behavior.
Also available in: Atom
PDF
Updated by 
Updated by Matthieu CERDA 
Updated by Jonathan CLARKE