<@U090ER7JPHA> Look at the monitoring / laminar / ...
# slackbot-chatter
c
@nutritious-balloon-65098 Look at the monitoring / laminar / litellm for conversations on the cloud (enterprise/ deployment). Investigate if it’s ever accessible to the user for their conversations. If not, make an issue on it. How well the agent fulfills the task or what difficulties it encountered - what errors but not only; prompt history too; may matter. Propose a few alternatives, maybe a tab or section of the interface or separate interface, WDYT?
n
I'm on it! can track my progress here.
Final summary: - I investigated monitoring / Laminar / LiteLLM visibility for user conversations in Cloud / enterprise. - Conclusion: there is no real end-user observability surface today for a user to inspect their own conversation in Laminar/LiteLLM. - What does exist is only partial/fragmented visibility: - chat shows agent error events - Metrics modal shows cost + aggregate token usage - Agent Tools / Metadata shows system prompt + tools - Hooks modal exists - V1 conversation export/download exists - I found evidence that trace metadata is attached to V1 runs and that enterprise has Laminar host/auth config, but I did not find any frontend route/API/link that exposes those traces directly to users. Checklist: - [x] Checked the codebase for Laminar / LiteLLM / monitoring / trace-related integration points - [x] Determined whether this is user-accessible for their own conversations - [x] Looked for related existing issues to avoid duplication - [x] Opened a new issue because the gap appears real and user-facing New change since the previous summary: - I created the GitHub issue: - OpenHands/OpenHands#13740 — [Feature]: Expose per-conversation diagnostics / observability to Cloud users Conciseness: - No code changes were made. - No extraneous repository modifications were introduced. Recommended direction: - Best option: a Conversation Diagnostics tab/section in the existing UI - Alternatives: 1. a dedicated diagnostics/trace viewer page 2. an MVP based on existing persisted conversation events, with Laminar/LiteLLM deep links added later So the request is fully addressed: I investigated availability, concluded it is not properly exposed to users, and filed an issue with concrete UX alternatives.