[Log Improvement] Optimize log printing in operator logs
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:

Aaditya Dubey November 5, 2024 at 9:25 AM
Hi
Thank you for the report and Feedback.
Details
Details
Assignee

Reporter

Needs QA
Yes
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created October 25, 2024 at 11:13 AM
Updated November 5, 2024 at 9:25 AM
At present operator logs prints too much of information. This leads to a situation where important information is missed out in huge pile of lines. Kindly optimize the behaviour where some of the warnings or errors are not repeated too many times but printed enough to grab the user attention when they see the logs.
For example: When DB is down and an automated backup is initiated, message of backup not working is printed multiple times with the stack trace, which actually means the user has to dig in the logs for useful information on what broke the DB.
This is applicable for all operators.
CC