-
Notifications
You must be signed in to change notification settings - Fork 453
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
Use Kubeflow metadata for metrics collection #862
Comments
@jlewi @zhenghuiwang |
Out of the box integration with metadata would be awesome. |
Not sure the requirements of metadata. Now we only use katib-db to store metrics. If metadata does not require any other abstraction, I think it should be easy to support it. |
Related: #841 (comment) |
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. |
/lifecycle frozen |
/kind feature
Describe the solution you'd like
Right now Katib depends on logging the metrics to stdout (see #685).
It would be nice if instead Katib could be configured to use Kubeflow metadata to obtain the metrics.
Here's a strawman for how this might work
It seems natural for folks to instrument their code to log metrics to metadata.
Furthermore, using the metadata SDK to log metrics should mean logging metrics to metadata is no more difficult then logging to stdout.
A side benefit would be that this avoids some of the sideffects of using side cars to fetch logs from stdout (#685)
/cc @zhenghuiwang @johnugeorge @gaocegege
The text was updated successfully, but these errors were encountered: