Skip to content
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

[FEAT_REQ] Improve Third-Party Logging in Progress Viewer #209

Open
tomonarifeehan opened this issue Sep 22, 2024 · 0 comments
Open

[FEAT_REQ] Improve Third-Party Logging in Progress Viewer #209

tomonarifeehan opened this issue Sep 22, 2024 · 0 comments
Labels
good first issue Good for newcomers

Comments

@tomonarifeehan
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
The Progress Viewer tab currently displays logs related to model training, but it lacks comprehensive integration with third-party logging services (e.g., TensorBoard, Weights & Biases). This limitation makes it difficult for users to access detailed logs and visualizations directly within the Progress Viewer, forcing them to switch between multiple platforms to track training progress and performance metrics. This disrupts the workflow and makes monitoring and debugging model training cumbersome.

Describe the solution you'd like
Enhance the Progress Viewer by integrating third-party logging services, allowing users to view detailed logs, graphs, and performance metrics directly within the tab. This could include displaying real-time updates, loss curves, accuracy plots, and other visual data provided by these logging tools. The integration should be seamless, with clear options to connect third-party services, select which logs to display, and customize the view to suit the user’s preferences.

Describe alternatives you've considered

Providing a configurable API endpoint within the Progress Viewer to pull in logs from third-party sources without deep integration, giving users basic but direct access to external logging.
Allowing users to download logs from third-party services and manually upload them into the Progress Viewer for visualization, though this would still lack real-time functionality.

Additional context
Improving third-party logging within the Progress Viewer will streamline the model training workflow, reduce context switching, and provide a more unified view of training progress. Below are examples of other platforms that effectively integrate third-party logging, enhancing the usability and monitoring capabilities of the training process.

@tomonarifeehan tomonarifeehan added the good first issue Good for newcomers label Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant