Project

General

Profile

Architecture #11027

We are identifying agent runs based on hasPolicyServer-*, which is inefficient, and invalid

Added by Nicolas CHARLES 6 months ago. Updated 4 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Target version (plugin):
Effort required:
Small

Description

Only nodes with rule hasPolicyServer-* can have their reports processed by the webapp
However dsc nodes don't have this rule, so they rely on a hack to work

We ought to change the getRunsQuery in ReportsJdbcRepository to:
  • remove the hasPolicyServer%
  • filter on control report type

so that it would work everywhere


Subtasks

Architecture #11039: Update start/end reports in rudder techniquesReleasedAlexis MOUSSET

Architecture #11085: Adapt CLI to accept new end run formatReleasedNicolas CHARLES

Architecture #11100: Same as 11085 for 4.1ReleasedNicolas CHARLES

Associated revisions

Revision 5b7d9f50
Added by Nicolas CHARLES 6 months ago

Fixes #11027: We are identifying agent runs based on hasPolicyServer-*, which is inefficient, and invalid

History

#1 Updated by Nicolas CHARLES 6 months ago

we ùay need to add an index on eventtype (but that's not even sure) or eventtype = 'log_info'

#2 Updated by Benoît PECCATTE 6 months ago

  • Tracker changed from Bug to Architecture
  • Subject changed from We are identifying agent runs based on hasPolicyServer-*, which is unefficient, and invalid to We are identifying agent runs based on hasPolicyServer-*, which is inefficient, and invalid

#4 Updated by Nicolas CHARLES 6 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES

#5 Updated by Nicolas CHARLES 6 months ago

  • Description updated (diff)

We decided to change the format of reports to
severity: control
technique : rudder
directive: run
serial: 0
rule: rudder
component: end/start
value : $configid

#6 Updated by Nicolas CHARLES 6 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/1688

#7 Updated by Nicolas CHARLES 6 months ago

  • Status changed from Pending technical review to Pending release

#8 Updated by Vincent MEMBRÉ 5 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.2.0~beta2 which was released today.

Also available in: Atom PDF