Project

General

Profile

Actions

Architecture #25385

closed

We need a reportingLogic computing on percent

Added by François ARMAND 4 months ago. Updated 4 months ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

Description

In the following example, to

1.1 - FS
  - 1.1.1 - Modules
      - 1.1.1.2 HFS module => == enforce (reportingLogic == ignoreNA ?)
        block(audit or enforce) CCC ? 
        Audit: 100% N/A
            - block(audit) => 100% N/A
        Enforce:  BBB ?
            - block(enforce)
              - block(step1) AAA ?
                 - gm1 0% (100% error)
                 - gm2 100%
                 - gm3 (100% N/A)
            - block(step2)
               - gm1 100%
            - block(step3)
               - gm1 100%

      - 1.1.1.2 (disabled: N/A) DDD ?

Hypothesis:
AAA: today, that can give 33% (weitghed) or 0% (worst). Say we use the 33% case (typically for an iteration).

Problems:
- BBB: today, we can only have reporting logic that gives 80% (weighted) or 0% (worst case). We need to be able to 33% (worst in compliance)
- CCC: at that level, we want to ignore N/A and use a "worst..." that like in BBB gives 33%.
- DDD: we need to be able to choose if that N/A count (as a success) for 1.1.1 or not, and so if the result is 33% or 66%.

A common trait seems to be that each leaf item is weighted "100", not the number of checks that lead to that, which is opaque.

I don't know if we need a need `reportingLogic` (worst wheighted base 100 or something like that) or count the percent at a level (ie keep the existing reporting logic, but with an additional parameter), or something else.


Related issues 1 (0 open1 closed)

Is duplicate of Rudder - User story #25383: Worst report takes the worst component instead of blockReleasedFrançois ARMANDActions
Actions #1

Updated by François ARMAND 4 months ago

  • Subject changed from We need a reportingLogic that to We need a reportingLogic comuting on percent
Actions #2

Updated by François ARMAND 4 months ago

  • Subject changed from We need a reportingLogic comuting on percent to We need a reportingLogic computing on percent
Actions #3

Updated by Clark ANDRIANASOLO 4 months ago

  • Has duplicate User story #25383: Worst report takes the worst component instead of block added
Actions #4

Updated by François ARMAND 4 months ago

  • Has duplicate deleted (User story #25383: Worst report takes the worst component instead of block)
Actions #5

Updated by François ARMAND 4 months ago

  • Is duplicate of User story #25383: Worst report takes the worst component instead of block added
Actions #6

Updated by François ARMAND 4 months ago

  • Status changed from New to Rejected

Closing this one, it is less intrusive for now to just add a new reporting logic kind (done in linked ticket #25383)

Actions

Also available in: Atom PDF