Project

General

Profile

Actions

User story #25383

open

Worst report takes the worst component instead of block

Added by Clark ANDRIANASOLO 29 days ago. Updated 16 days ago.

Status:
Pending release
Priority:
1 (highest)
Category:
Web - Compliance & node report
Target version:
UX impact:
It bothers me each time
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Name check:
To do
Fix check:
To do
Regression:
No

Description

In the following scenario of reporting with the "worst" reporting logic, the root block result is surprising :

block1 : worst => 0% error
  - block11: weighted => 33% error
     - gm1: 0%
     - gm2: 100%
     - gm3: 100%
  - block12: weighted => 100% success
     - gm4: 100%
     - gm5: 100%

We expect a worst of 33%, as if the block11 itself is the worst component

UPDATE: we need a new reporting logic kind, because both make sense in different contexte (the other one when we base our logic on the compliance level structure, not the percent). I'm updating the type of tracker accordingly.


Related issues 1 (0 open1 closed)

Has duplicate Rudder - Architecture #25385: We need a reportingLogic computing on percentRejectedActions
Actions

Also available in: Atom PDF