Error Analysis: anchor the detail view to the clicked cause exception
Author: feelformCreated Aug 26, 2026Updated Aug 26, 2026
A chain renders as multiple exception rows in the call tree (e.g. NestedServletException and its cause IllegalArgumentException), all sharing the same errorKey. Clicking a cause row opens Error Analysis, but the detail view always starts at the top (the outermost exception) — it does not scroll to the clicked cause.
Expected: opening Error Analysis from a cause row anchors the detail view to that cause's card.
Tasks:
- Identify the clicked cause in the detail view — match the row's exception class name against
ExceptionDetailView.errorClassName(chains repeating the same class need a tie-breaker) - Scroll the detail view to the matched cause card on open
Starting points:
web-frontend/.../Transaction/call-tree/callTreeTableColumns.tsx— link carrieserrorKeyonly; no per-cause identifierweb-frontend/.../ErrorAnalysis/error-detail/ErrorAnalysisErrorDetailFetcher.tsx— renders the chain as cards;ExceptionDetailView.exceptionDepthdistinguishes causes
Source: pinpoint-apm/pinpoint