You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
We may often meet a situation that everything seems Ok on the UI,the status of experiment and trials are remaining running, but actually there are something wrong have already happened with the experiment and trials.
To determine if everything is ok, we have to use commands like kubectl logs and kubectl describe to check logs and Events of almost every resource associating katib experiment. This is very unfriendly for data scientists, who may want focus on machine learning problems.
Therefore, I suggest to display more detailed information and logs of experiment on the user interface, make us easy to know if the experiment and trials are actrually runing well from the UI.
[Miscellaneous information that will assist in solving the issue.]
Love this feature? Give it a 👍 We prioritize the features with the most 👍
The text was updated successfully, but these errors were encountered:
@javen218 this makes total sense, and it's the direction we are also heading towards. We want users to be able to do every kubectl action via the UI, which includes exposing logs, events etc.
We have also started an effort to create distinct pages for each Trial, to expose more such information #1763#1783. Next steps we could do in parallel would be exposing events for both Experiment and Trial objects.
Also for anyone wanting to contribute, we can break this into smaller tasks to help with this effort.
/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
We may often meet a situation that everything seems Ok on the UI,the status of experiment and trials are remaining running, but actually there are something wrong have already happened with the experiment and trials.
To determine if everything is ok, we have to use commands like
kubectl logs
andkubectl describe
to check logs and Events of almost every resource associating katib experiment. This is very unfriendly for data scientists, who may want focus on machine learning problems.Therefore, I suggest to display more detailed information and logs of experiment on the user interface, make us easy to know if the experiment and trials are actrually runing well from the UI.
[Miscellaneous information that will assist in solving the issue.]
Love this feature? Give it a 👍 We prioritize the features with the most 👍
The text was updated successfully, but these errors were encountered: