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

Add Network Status Monitoring for Backend LLM Communication #779

Open
omar-sadiqi opened this issue Dec 16, 2024 · 1 comment
Open

Add Network Status Monitoring for Backend LLM Communication #779

omar-sadiqi opened this issue Dec 16, 2024 · 1 comment

Comments

@omar-sadiqi
Copy link

Description:
Currently, there is no way to monitor the network status while communicating with the backend LLMs. This makes it difficult to debug issues related to connectivity, API requests, and responses. Adding a feature to track and display the network status would greatly improve the developer experience and help identify issues more effectively.

Proposed Solution:

Network Activity Panel:
Add a panel to the UI that displays network activity related to LLM communication. This panel should include:

The status of ongoing requests (e.g., pending, completed, failed).
The request and response payloads (for debugging purposes).
Error messages or codes in case of failures.
Status Indicators:
Introduce real-time status indicators for:

API connectivity (e.g., connected, disconnected).
Backend LLM health checks or availability.
Logging and History:

Log all network requests and responses in a debug console.
Allow exporting logs for external debugging and issue reporting.
Benefits:

Improved Debugging: Developers can quickly identify if issues stem from the network, the backend LLM, or the frontend.
Enhanced Visibility: Real-time insights into request/response status can streamline troubleshooting.
Community Contributions: Easier debugging could encourage contributors to submit more precise bug reports and fixes.
Potential Challenges:

May require adjustments to existing middleware to capture and display network activity.
Ensuring sensitive information (e.g., API keys) is redacted in logs and UI displays.
Additional Context:
This feature would be especially helpful for developers integrating new LLMs or debugging API-level issues in production environments. It aligns well with bolt.diy’s mission of being an accessible and extensible platform for developers using LLMs.

Acceptance Criteria:

A visible UI component to monitor network status.
Real-time updates for network activity related to LLM communication.
Logging and export capabilities for network activity.
Feel free to comment or suggest any additional requirements for this feature. 🚀

@leex279
Copy link

leex279 commented Dec 17, 2024

Hey,
did you see the event logging in settings? Is this what you mean? Maybe a enhanced version of it with more infos?
image

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

No branches or pull requests

2 participants