Project

General

Profile

Actions
Copy link

User story #13642

open

Know the name of the directives/rules that configured something on agent side

Added by Nicolas CHARLES about 6 years ago. Updated almost 2 years ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
Ideas (not version specific)
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Name check:
Fix check:
Regression:

Description

On the agent side, we only have ruleid@@directiveid to identify a report, and some partial info on the naming in the rudde-directives (as directives are agregated)
It makes it super hard to debug what is going on: for instance, if a variable is set twice via generic variable definition, we only know via the directiveid which directive configured, and we have to look in the interface for the directive name

It would make debuging much easier to have all directiveid > directivenames and ruleid>rulename, exposed in verbose output

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.16 to 4.1.17
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 4.1.17 to 4.1.18
  • Priority changed from 48 to 0
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 4.1.18 to 4.1.19
Actions
Copy link
 #5

Updated by Alexis Mousset almost 6 years ago

  • Target version changed from 4.1.19 to 4.1.20
Actions
Copy link
 #6

Updated by François ARMAND almost 6 years ago

  • Target version changed from 4.1.20 to 4.1.21
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.21 to 4.1.22
Actions
Copy link
 #8

Updated by Nicolas CHARLES over 5 years ago

we do have these value at generation time:

      "only root/Test-flip-flop-1"                                                     usebundle => rudder_reporting_context("735fb320-dada-4231-bb9c-8d6887ae16d3","e5d1808e-f71e-41e7-a177-67c5733b76ff","Test_flip_flop_1");
      "only root/Test-flip-flop-1"                                                     usebundle => set_dry_run_mode("false");
      "only root/Test-flip-flop-1"                                                     usebundle => enable_reporting;
      "only root/Test-flip-flop-1"                                                     usebundle => Test_flip_flop_1;
      "only root/Test-flip-flop-1"                                                     usebundle => clean_reporting_context;

so we could have an extended rudder_reporting_context with names

Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.22 to 4.1.23
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.23 to 4.1.24
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 4.1.24 to 588
Actions
Copy link
 #13

Updated by Alexis Mousset over 5 years ago

  • Target version changed from 588 to 5.0.13
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.15 to 5.0.16
Actions
Copy link
 #17

Updated by Alexis Mousset almost 5 years ago

  • Target version changed from 5.0.16 to 5.0.17
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.17 to 5.0.18
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.18 to 5.0.19
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 5.0.20 to 797
Actions
Copy link
 #22

Updated by Benoît PECCATTE over 3 years ago

  • Target version changed from 797 to 6.1.14
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions
Copy link
 #28

Updated by Alexis Mousset almost 3 years ago

  • Tracker changed from Bug to User story
  • Subject changed from It's not possible, in the agent, to know the name of the directives/rules that configured something to Know the name of the directives/rules that configured something on agent side
  • Severity deleted (Minor - inconvenience | misleading | easy workaround)
  • Priority deleted (0)

It is not a bug.

Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
Copy link
 #32

Updated by Alexis Mousset almost 2 years ago

  • Target version changed from old 6.1 issues to relocate to Ideas (not version specific)
Actions
Copy link

Also available in: Atom PDF