Project

General

Profile

Actions

Bug #9853

closed

Incomplete logging in debug_timming

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

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

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

Actions #1

Updated by Nicolas CHARLES about 6 years ago

  • Status changed from New to In progress
Actions #2

Updated by Nicolas CHARLES about 6 years 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
Actions #3

Updated by Nicolas CHARLES about 6 years ago

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

Updated by Vincent MEMBRÉ almost 6 years 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.

Actions

Also available in: Atom PDF