Skip to content

Conversation

@skeeey
Copy link
Contributor

@skeeey skeeey commented Oct 20, 2025

  1. using info as default log level for zap log in maestro server
  2. using -v=2 as default log level for klog in sdk-go (🌱 using context log open-cluster-management-io/sdk-go#151)

We only log the request metadata in these log levels

@skeeey
Copy link
Contributor Author

skeeey commented Oct 20, 2025

/assign @clyang82

@skeeey skeeey force-pushed the log branch 2 times, most recently from cb4c3c1 to 22ae793 Compare October 20, 2025 08:30
viper.SetConfigFile(logConfigFile)
// default log level is info
viper.SetDefault(varLogLevel, "info")
logger.SetLogLevel("info")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is related with #268. we allow to modify the log level in runtime.

Copy link
Contributor Author

@skeeey skeeey Oct 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, we still allow to modify the log level in runtime, but we should not use viper.SetDefault to set default log level, it does not work

Copy link
Contributor

@clyang82 clyang82 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@clyang82
Copy link
Contributor

Please reply in the thread to tell SRE to use 2 in their environment.

@clyang82 clyang82 merged commit c3a2037 into openshift-online:main Oct 21, 2025
9 checks passed
@skeeey skeeey deleted the log branch October 24, 2025 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants