Bug #8344: Missing relevant information about why the compliance is what it is on node - Rudder - Issue Tracker

Actions

Copy link

Bug #8344

closed

Bug #8051: Compliance is not correctly computed if we receive run agent right after generation

Missing relevant information about why the compliance is what it is on node

Added by François ARMAND over 8 years ago. Updated over 8 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

Nicolas CHARLES

Category:

Web - Compliance & node report

Target version:

3.0.16

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

In case like #8051, it would be much, much clearer if the information that we have with the log:

  <logger name="explain_compliance.root" level="trace" additivity="false">
    <appender-ref ref="OPSLOG" />
    <appender-ref ref="STDOUT" />
  </logger>

were also available directly on the UI. It would also be very helpful to have information when we have couple of missing/unexpected, telling us that most likelly, the agent is sending report for a different config id.