-
Notifications
You must be signed in to change notification settings - Fork 80
CORTX-30044 Redirect hare log messages to stdout/stderr #2148
Conversation
d090810
to
67a460a
Compare
retest this please |
@seagate-sarang-sawant, please fix the commit message with respect to following points,
|
Problem: a) kubectl logs display debug message and stream handlers are missing from some hare processes. b) log level is incorrect for some log messages in cfgen and hax Solution: a) stream handlers added to cfgen, cli, update_conf, consul and hax starters with info as default log level. b) Stream handlers would have INFO level logging with format change like process id or thread added in log message depending on context.Log level of some messages in cfgen are changed to info from debug. Signed-off-by: Sarang Sawant <sarang.sawant@seagate.com>
67a460a
to
b71c2cf
Compare
@seagate-sarang-sawant, so now do you see the info messages in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good in general. Please post the output of kubectl logs
as requested. Thank you.
Kubectl logs for cortx-hax, cortx-setup containers [root@ssc-vm-rhev4-2619 ~]# kubectl logs -f -c cortx-hax cortx-data-g0-0 [root@ssc-vm-rhev4-2619 ~]# kubectl logs -c cortx-setup cortx-data-g0-0 [root@ssc-vm-rhev4-2619 ~]# kubectl logs -c cortx-setup cortx-ha-f9748b9f-g4zzc [root@ssc-vm-rhev4-2619 ~]# kubectl logs -c cortx-setup cortx-client-0 |
Can we remove this duplicate messages, is it expected. |
Problem: Redirect Error and Warning messages of Hare processes to stdout/stderr
Solution: Add stream handler to processes missing it. Stream handlers would
have INFO level logging with process id or thread added in log message
depending on context. Log level of some messages are changed to info
from debug.
Signed-off-by: Sarang Sawant sarang.sawant@seagate.com