Project

General

Profile

Actions

User story #3048

closed

Send non compliant report log and opslog to local syslog

Added by Vincent MEMBRÉ about 12 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
3
Assignee:
-
Category:
System integration
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Some of the precious informations we log in /var/log/rudder should be logged in local syslog.

We should do that for :
  • non compliant reports log (#2988)
  • sysadmin log (#2427)

We should use the local way to insert those logs ( so not using the syslog port, which is not the local way to use syslog)

Actions #1

Updated by Jonathan CLARKE about 12 years ago

  • Target version set to 2.5.0~beta1
Actions #2

Updated by Jonathan CLARKE about 12 years ago

  • Target version deleted (2.5.0~beta1)
Actions #3

Updated by François ARMAND about 12 years ago

  • Target version set to Ideas (not version specific)
Actions #4

Updated by Jonathan CLARKE almost 12 years ago

  • Category changed from 11 to 39
Actions #5

Updated by Benoît PECCATTE almost 10 years ago

  • Category changed from 39 to System integration
Actions #6

Updated by François ARMAND over 4 years ago

  • Status changed from New to Rejected

We did a lot of work on logs since that time, and people don't really want to see rudder strange reports in their logs.

Actions

Also available in: Atom PDF