Project

General

Profile

Bug #57061

Use single cluster log level (mon_cluster_log_level) config to control verbosity of cluster logs while logging to external entities

Added by Prashant D over 1 year ago. Updated over 1 year ago.

Status:
Fix Under Review
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

We donot control the verbosity of the cluster logs which are getting logged to stderr, graylog and journald. Each LogEntry gets logged as it is whether it's at DBG/INF/WRN/ERR level to stderr, graylog and journald. The verbosity of the cluster logs gets controlled only if LogEntry is getting logged to cluster log file (mon_cluster_log_file_level) and/or to syslog (mon_cluster_log_to_syslog_level).

We should have a single config parameter for cluster log level to control the cluster log verbosity irrespective of where cluster logs are getting logged to whether to cluster log file, syslog, journald, graylog etc.
Remove mon_cluster_log_file_level and mon_cluster_log_to_syslog_level to merge them to mon_cluster_log_level.

Refer BZ for more details : https://bugzilla.redhat.com/show_bug.cgi?id=2053021

History

#1 Updated by Prashant D over 1 year ago

  • Description updated (diff)

#2 Updated by Prashant D over 1 year ago

  • Description updated (diff)

#3 Updated by Prashant D over 1 year ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 47502

#4 Updated by Prashant D over 1 year ago

  • Backport set to pacific,quincy

#5 Updated by Prashant D over 1 year ago

  • Description updated (diff)

Also available in: Atom PDF