Implementation Approaches

How should we structure the Error Dashboard feature?

A

Full Build — Both Views Together

Build the Error Listing and Error Detail as a single feature. Ship both views at once with all panels (version track, callers, similar issues, notes, common payload, performance).

Pros

  • Complete experience from day one
  • Design decisions can be made holistically
  • Single backend API design pass

Cons

  • Large scope — long time to first usable version
  • Notes, similar issues, and common payload are exploratory features
  • Backend regression coefficient + notes endpoints needed upfront
B

Phased — Core First, Then Enrich ⟵ Recommended

Ship in 3 phases. Phase 1: Listing view + basic Detail (error info, histogram, statement link, performance). Phase 2: Version track, callers, trend sorting. Phase 3: Notes, similar issues, common payload.

Pros

  • Usable dashboard available quickly (Phase 1 uses existing APIs)
  • Phase 1 needs zero new backend endpoints
  • Exploratory features (notes, similar, payload) deferred until core is validated
  • Each phase delivers standalone value

Cons

  • Trend sorting (key UX goal) requires backend work → Phase 2
  • Users may want the full vision sooner
Phase breakdown:
P1: Listing (filters, sparklines, container cards, frontend-computed trends) + Detail (error info, 24h histogram, statement link, performance panel, stack issues)
P2: Backend regression coeff → trend sorting, version track + edge diff, callers from kitchen sink
P3: Notes system, similar issues query, common payload analysis
C

Listing-Only MVP

Build only the Error Listing view first. Clicking an error opens the existing error log panel/widget instead of a new detail page. Add the detail page later as a separate project.

Pros

  • Fastest to ship — smallest scope
  • Reuses existing error log widget for detail
  • Validates whether users want a workspace-level error view at all

Cons

  • The existing widget isn't designed for this context — awkward UX
  • Misses the core value proposition (regression discovery, version tracking)
  • Detail page would need to be designed separately later anyway