Project

General

Profile

Actions

Bug #5334

closed

The archiving logic of execution reports needs to be adapted for "error only" report mode

Added by Nicolas CHARLES over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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.


Related issues 1 (0 open1 closed)

Related to Rudder - User story #5293: Add a 'changes only' compliance mode, only reporting changes on systemsReleasedJonathan CLARKE2014-07-22Actions
Actions #1

Updated by François ARMAND over 9 years ago

  • Subject changed from Change the archiving logic in "report_only" mode to Change the archiving logic in "error only" report mode
Actions #2

Updated by François ARMAND over 9 years ago

  • 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
Actions #3

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions #4

Updated by Jonathan CLARKE over 9 years ago

  • 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.

Actions #5

Updated by Jonathan CLARKE over 9 years ago

  • Parent task deleted (#5293)
Actions #6

Updated by François ARMAND over 9 years ago

  • 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.

Actions #7

Updated by François ARMAND over 9 years ago

  • Status changed from New to Rejected

well, actually closing it because it makes no sense until we keep the curren timplemented behavior.

Actions

Also available in: Atom PDF