Project

General

Profile

Actions

Bug #4138

closed

Excessive logs from "Store Agent Run Times" task

Added by Jonathan CLARKE about 11 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
3
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On a fresh install of Rudder 2.8, I see these 2 messages in the logs every 5 seconds. This is far too much logging!

[2013-11-07 19:29:05] INFO  com.normation.rudder.reports.execution.ReportsExecutionService - [Store Agent Run Times] Task #127: Starting analysis for run times from 2013/11/07 19:29:00 up to 2013/11/07 19:29:05 (runs after SQL table ID 134)
[2013-11-07 19:29:05] INFO  com.normation.rudder.reports.execution.ReportsExecutionService - [Store Agent Run Times] Task #127: Finished analysis in 12 ms. Added or updated 0 agent runs (up to SQL table ID 134)

Let's change this log's priority to DEBUG. However, if the task takes too long (I think there is already a log for that, use the same condition for "too long"), make sure the message is in WARN level.

Actions #1

Updated by François ARMAND about 11 years ago

Vincent, this one is trivial, do it as soon as possible.

Actions #2

Updated by Vincent MEMBRÉ about 11 years ago

Should we not have a dedicated logger for it (only in webapp logs)?
So we can change it's verbosity so it does not mess up with other debug process?

However I can already change their verbosity.

Actions #3

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from 8 to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/367
Actions #4

Updated by Vincent MEMBRÉ about 11 years ago

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

Updated by Anonymous about 11 years ago

Actions #6

Updated by Nicolas PERRON about 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.8.1, which was released today.
Check out:

Actions #7

Updated by Benoît PECCATTE almost 10 years ago

  • Category changed from 39 to System integration
Actions

Also available in: Atom PDF