-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enrich logging #112
Comments
We prefer logrus in the community, I think. Since it supports structured logging. |
@YujiOshima can we make this issue more specific this will make it easier to get help from the community? Here are some questions for you:
|
Logging Component:
BayseOpt Suggestion is implemented with python. I don't know which log liberally is better for python. Metadata: Integration with Prometheus sounds nice. It enable monitoring across languages. @gaocegege @jlewi BTW, this library https://github.com/uber-go/zap looks nice since it is faster than logrus. WDYT? |
I love zap, while we are using logrus now. I think we could use zap in katib if you like as a feasibility research. |
@gaocegege Thanks! Lets's try zap for Katib. As zap is also structured with key-value, we can migrate logrus easily when we need. |
Yeah, I opened an issue here: kubeflow/training-operator#534 I closed it because I think the performance of the logging is not the bottleneck. If the migration is painless, I am glad to use zap. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it. |
Currently, the logs of Katib components are so poor.
We need enrich logs in the debug, verbose, and info level.
Maybe we should introduce
glog
pkg.The text was updated successfully, but these errors were encountered: