Project

General

Profile

Actions
Copy link

User story #4520

closed

Don't write execution report in several log files

User story #4520: Don't write execution report in several log files

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

Status:
Released
Priority:
2
Assignee:
Jonathan CLARKE
Category:
Performance and scalability
Target version:
2.10.0~beta1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Today, we are writing node execution reports in at least 3 places:

- all.log,
- webapp logs,
- database.

There is absolutly no need to write them in both webapp logs and all.log. Moreover, they tends to make webapp logs unreadable.
And all.log should be rename with a correct name (node-reports.log ? node-execution.log ?)

Subtasks 2 (0 open — 2 closed)

User story #4602: Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.logReleasedJonathan CLARKEActions
User story #4603: Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log (for relay servers)ReleasedNicolas CHARLESActions

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #1

François ARMAND wrote:

Today, we are writing node execution reports in at least 3 places:

- all.log,
- webapp logs,
- database.

There is absolutly no need to write them in both webapp logs and all.log. Moreover, they tends to make webapp logs unreadable.
And all.log should be rename with a correct name (node-reports.log ? node-execution.log ?)

Actually, I'm not sure this is quite right. I agree for all.log and database, but there is also linuxlog.log (also could be renamed, or winlog.log).

However, I don't see where the webapp writes these out?

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #2

We used to have extLinuxReport.log as well, but since cfengine 3.5 it's not populated anymore

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #3

I guess Francois is refering to the /var/log/rudder/compliance/non-compliant-reports.log

I agree we should drop all.log (or linuxlog.log). The original idea what to have a file with all reports received, one for all reports received from Rudder on linux (linuxlog) and one for all windows system (winlog)
the naming was really poor (I'm responsible for that), and there is a lot of duplications there.

Updated by François ARMAND almost 12 years ago Actions
Copy link
 #4

More info:

- we are keeping /var/log/rudder/compliance/non-compliant-reports.log: it's a post-proccessed file, with valuable information
- we don't keep linuxlog.log nor windowslog.log
- we keep all.log
- there is no need to update logrotate configuration

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #5

  • Status changed from New to 14

Updated by Jonathan CLARKE almost 12 years ago Actions
Copy link
 #6

  • Status changed from 14 to Pending release
  • Assignee set to Jonathan CLARKE

Updated by Vincent MEMBRÉ over 11 years ago Actions
Copy link
 #7

  • Category changed from Performance and scalability to 39

Updated by Vincent MEMBRÉ over 11 years ago Actions
Copy link
 #8

  • Category changed from 39 to Performance and scalability

Updated by Vincent MEMBRÉ over 11 years ago Actions
Copy link
 #9

  • Status changed from Pending release to Released

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

The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000084.html
    The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
    Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions
Copy link

Also available in: PDF Atom