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 #1

Updated by Clark ANDRIANASOLO 29 days ago

  • Status changed from New to In progress
Actions #2

Updated by Clark ANDRIANASOLO 29 days ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/5846
Actions #3

Updated by Clark ANDRIANASOLO 29 days ago

Actions #4

Updated by Clark ANDRIANASOLO 22 days ago

  • Target version changed from 8.1.7 to 8.2.0~beta1
  • Priority changed from 60 to 30

This is targeting 8.2 because of techniques compatibility issues that could be introduced by adding a new type of reporting logic in 8.1

Actions #5

Updated by Vincent MEMBRÉ 21 days ago

  • Target version changed from 8.2.0~beta1 to 8.2.0~beta2
  • Priority changed from 30 to 60
Actions #6

Updated by François ARMAND 21 days ago

Actions #7

Updated by François ARMAND 21 days ago

Actions #8

Updated by François ARMAND 21 days ago

  • Tracker changed from Bug to User story
  • Description updated (diff)
  • Severity deleted (Minor - inconvenience | misleading | easy workaround)
  • Priority deleted (60)
Actions #9

Updated by Clark ANDRIANASOLO 17 days ago

  • Status changed from Pending technical review to Pending release
Actions #10

Updated by François ARMAND 16 days ago

  • Priority changed from N/A to 1 (highest)
Actions

Also available in: Atom PDF