Project

General

Profile

Actions

User story #5359

closed

User story #5894: Add a logger to trace webapp bootstrap actions

Add a logger to trace bootstrap action and clean them

User story #5359: Add a logger to trace bootstrap action and clean them

Added by François ARMAND over 11 years ago. Updated over 10 years ago.

Status:
Released
Priority:
5 (lowest)
Category:
System integration
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

With a list of action (essentially checks) executed when Rudder web application starts.

But at boot time, Rudder is not saying that it is doing things, and we just think that it stalled.
So we want to have output saying "existing blabla"

Moreover, it may be intersting to know how much time each of these action is taking to help identifies bad behaviour for debugging (so at debug level).

The output in info level is:

[2014-09-30 13:30:03] INFO  bootchecks - Check mandatory DIT entries
[2014-09-30 13:30:04] INFO  application - All the required DIT entries are present in the LDAP directory
[2014-09-30 13:30:04] INFO  bootchecks - Check initialization of User Technique Library
[2014-09-30 13:30:04] INFO  bootchecks - Check event log migration format 4 -> 5

And in debug:

[2014-09-30 13:16:15] INFO  bootchecks - [#0] Check mandatory DIT entries
[2014-09-30 13:16:16] INFO  application - All the required DIT entries are present in the LDAP directory
[2014-09-30 13:16:16] DEBUG bootchecks - [#0] Check mandatory DIT entries: OK in [951 ms]
[2014-09-30 13:16:16] INFO  bootchecks - [#1] Check initialization of User Technique Library
[2014-09-30 13:16:16] DEBUG bootchecks - [#1] Check initialization of User Technique Library: OK in [51 ms]
[2014-09-30 13:16:16] INFO  bootchecks - [#2] Check event log migration format 4 -> 5
[2014-09-30 13:16:16] INFO  migration - No migration detected by migration script (table 'migrationeventlog' is empty or does not exists)
[2014-09-30 13:16:16] DEBUG bootchecks - [#2] Check event log migration format 4 -> 5: OK in [105 ms]

Updated by François ARMAND over 11 years ago Actions #1

  • Status changed from In progress to 10
  • Pull Request set to https://github.com/Normation/rudder/pull/596

Updated by François ARMAND over 11 years ago Actions #2

  • Assignee changed from François ARMAND to Jonathan CLARKE

Updated by François ARMAND about 11 years ago Actions #3

  • Status changed from 10 to In progress
  • Assignee changed from Jonathan CLARKE to François ARMAND

The output is not clean for now.

Updated by François ARMAND about 11 years ago Actions #4

  • Subject changed from Add a logger to trace bootstrap action to Add a logger to trace bootstrap action and clean them
  • Description updated (diff)

Updated by François ARMAND about 11 years ago Actions #5

  • Status changed from In progress to Pending release
  • % Done changed from 0 to 100

Updated by François ARMAND about 11 years ago Actions #6

  • Description updated (diff)
  • Status changed from Pending release to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • % Done changed from 100 to 0

Updated by François ARMAND about 11 years ago Actions #7

The commit noted is NOT in rudder branches, its on "ust_5359/log_bootstrap_checks" which was pushed by error.
So, there is actually a TR to review and merge into master.

Updated by Jonathan CLARKE about 11 years ago Actions #8

  • Description updated (diff)
  • Status changed from Pending technical review to Discussion
  • Assignee changed from Nicolas CHARLES to François ARMAND

Updated target log formats.

Updated by François ARMAND about 11 years ago Actions #9

  • Description updated (diff)

Updated by François ARMAND about 11 years ago Actions #10

  • Status changed from Discussion to Pending technical review

Functionnaly validated and PR updated

Updated by François ARMAND about 11 years ago Actions #11

  • Assignee changed from François ARMAND to Nicolas CHARLES

Updated by François ARMAND about 11 years ago Actions #12

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

Updated by Matthieu CERDA about 11 years ago Actions #14

  • Target version changed from 140 to 3.0.0~beta1

Updated by Vincent MEMBRÉ about 11 years ago Actions #15

  • Parent task set to #5894

Updated by Vincent MEMBRÉ about 11 years ago Actions #16

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.

Updated by Benoît PECCATTE almost 11 years ago Actions #17

  • Category changed from 39 to System integration

Updated by Benoît PECCATTE over 10 years ago Actions #18

  • Tracker changed from Enhancement to User story
Actions

Also available in: PDF Atom