mon/LogMonitor: Use generic cluster log level config#47502
Conversation
|
jenkins test windows |
|
jenkins retest this please |
|
This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved |
Sure Sridhar. Let me add a testcase for it. |
de33fb2 to
c396885
Compare
|
jenkins test make check |
c396885 to
40a7e00
Compare
|
Thanks @idryomov. I saw your review comments a bit later. I have added the relevant section in PendingReleaseNotes for removing mon_cluster_log_*_level options. Let me address your review comments for standalone testcases. |
|
jenkins test make check |
|
The make check is failing due to tracker#63950. I have opened PR#55070 to fix it. |
|
@rzarzynski ACK |
|
@pdvian can you please review: /a/yuriw-2024-01-10_19:18:18-rados-wip-yuri3-testing-2024-01-10-0735-distro-default-smithi/7512554 |
|
@pdvian looks like this needs some changes. Feel free to re-add "needs-qa" when this is ready! |
Hi @NitzanMordhai, This testcase failed because the ceph cluster log messages were missing the loglevel in human readable format. I have opened a PR#49730 to fix this issue but could not get into main. The cluster logs were printing loglevel in numeric format : instead of : I have re-opened PR#49730 to address this issue. |
We do not control the verbosity of the LogEntry which is getting logged to stderr, graylog and journald. This causes excessive flooding of logs to /var/log, making a filesystem to fill up quickly. Also we have different config variables namely mon_cluster_log_file_level and mon_cluster_log_to_syslog_level to control verbosity at cluster log file and syslog level respectively. Add a generic cluster log level config variable which controls cluster log verbosity for all external entities. Additionally, this patch addresses the regression of `mon_cluster_log_file_level` option which doesn't take effect because of code refactoring of LogMonitor::update_from_paxos (commit : 7c84e06). Fixes: https://tracker.ceph.com/issues/57061 Fixes: https://tracker.ceph.com/issues/57049 Signed-off-by: Prashant D <pdhange@redhat.com>
|
jenkins test api |
|
Not sure it's related: |
|
jenkins test api |
We do not control the verbosity of the LogEntry
which is getting logged to stderr, graylog and
journald. This causes excessive flooding of logs
to /var/log, making a filesystem to fill up quickly.
Also we have different config variables namely
mon_cluster_log_file_level and mon_cluster_log_to_syslog_level
to control verbosity at cluster log file and
syslog level respectively. Add a generic cluster log
level config variable which controls cluster log
verbosity for all external entities.
Fixes: https://tracker.ceph.com/issues/57061
Signed-off-by: Prashant D pdhange@redhat.com
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows