Project

General

Profile

Bug #9853

Incomplete logging in debug_timming

Added by Nicolas CHARLES 12 months ago. Updated 10 months ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

Description

Most of the cost of compliance computation is not logged on debug_timing, making it hard to detect what is slow and what is not

Associated revisions

Revision d48c2d4d
Added by Nicolas CHARLES 12 months ago

Fixes #9853: Incomplete logging in debug_timming

History

#1 Updated by Nicolas CHARLES 12 months ago

  • Status changed from New to In progress

#2 Updated by Nicolas CHARLES 12 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1408

#3 Updated by Nicolas CHARLES 12 months ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#4 Updated by Vincent MEMBRÉ 10 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.3 and 4.1.0~beta3 which were released today.

Also available in: Atom PDF