Skip to content

Add Sentry Error Intelligence dashboard with Slack search#1035

Draft
liamdebeasi wants to merge 23 commits into
mainfrom
ai_main_f999ab047fe546908e3f
Draft

Add Sentry Error Intelligence dashboard with Slack search#1035
liamdebeasi wants to merge 23 commits into
mainfrom
ai_main_f999ab047fe546908e3f

analytics: thread summarization + unified thread fetching

6ab24c2
Select commit
Loading
Failed to load commit list.
Builder.io Integration / Review Agent completed Jun 2, 2026 in 5m 40s

5 potential issues found

Code Review Summary — PR #1035: Sentry Error Intelligence Dashboard

This PR adds a new "Sentry Error Intelligence" dashboard to the analytics template with rich error analysis, escalation detection, and enhanced Slack/GitHub integration. The feature includes:

  • New sentry-errors dashboard with top-10 error analysis, escalation detection, and related error grouping
  • Sentry org slug support via new data source field for proper multi-org configuration
  • Enhanced Slack search with optional user-token support and intelligent fallback (fuzzy search with bot token)
  • GitHub blame integration exposing commit history and contributor context for errors
  • Thread enrichment fetching full Slack conversation context alongside search results

Architecture Assessment: The implementation is well-structured with proper separation of concerns (UI components, actions, server-side integrations), appropriate credential handling, and good error fallback patterns. Type safety is solid throughout.

Risk Classification: Standard risk (analytics feature addition, no breaking API changes, no database schema modifications).

Key Findings

Critical Issues: 🔴

  • Missing function import breaks Slack user-token search (ReferenceError at runtime)

Should-Fix Issues: 🟡

  • GitHub blame feature shipped but not integrated into the dashboard UI
  • Slack secondary-workspace searches use wrong user token credential
  • Sensitive Slack search content and queries leaked to server logs
  • Slack URL matching has trailing-slash normalization issue
  • Unused Sentry stats query adds unnecessary API overhead

Positives:

  • Proper credential scoping and access control
  • Well-designed async error handling and fallbacks
  • Correct React patterns (memoization, hook dependencies)
  • Thoughtful API integration (Slack, GitHub, Sentry)

🧪 Browser testing: Will run after this review (PR touches UI code)