Bug #57061: Use single cluster log level (mon_cluster_log_level) config to control verbosity of cluster logs while logging to external entities - RADOS - Ceph

Actions

Copy link

Bug #57061

open

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 6 days ago.

Status:

Pending Backport

Priority:

Normal

Assignee:

Prashant D

Category:

Target version:

% Done:

Source:

Tags:

Backport:

quincy, reef

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(RADOS):

Pull request ID:

47502

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