Gadoes builds a control room for dispumike's outside connections

Operators can now see which data and tool sources are slow or failing before users feel it.

infrastructureanalytics

Legal AI tools like dispumike rarely work alone - they reach out to outside systems for documents, search, and other services through a common plumbing layer that lets the assistant pull from those sources. When one of those sources gets slow or starts erroring, the usual way you find out is a frustrated user.

Gadoes closed that gap. There's now an admin dashboard that tracks every connected source separately: how often its calls succeed, how fast it responds, and how many errors it has thrown in the last 24 hours. The page refreshes itself every minute, and the logging is built to stay out of the way - if recording a stat fails, it never disrupts the actual work. The 24-hour error count is the one to watch: it's the early warning that a source is degrading.

So what Anyone running a legal AI in production on top of several integrations should care - this is the difference between spotting a broken source yourself and hearing about it from an angry partner.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

4 commits from Gadoes/dispumike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
f7cb5d92 feat(chunk19): migration 005 - mcp_events telemetry table Gadoes 2026-05-02 ↗ GitHub
aabc7e28 feat(chunk19): telemetry logging in McpClientManager.callTool Gadoes 2026-05-02 ↗ GitHub
e37d7572 feat(chunk19): GET /admin/mcp-telemetry route with unit tests Gadoes 2026-05-02 ↗ GitHub
89fbb081 feat(chunk19): /admin/mcp-telemetry dashboard page with tests Gadoes 2026-05-02 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-27.md from inside the repo you want the changes in.

⬇ Download capture-thread-27.md