wu-sheng commented on issue #6784: URL: https://github.com/apache/skywalking/issues/6784#issuecomment-4671216237
The Horizon UI now implements this end-to-end, **entirely on the UI side — no OAP / query-protocol change and no SWIP needed** (the existing `queryBrowserErrorLogs` API already exposes what's required). **What landed (apache/skywalking-horizon-ui):** - A **Browser Errors** tab on the BROWSER layer listing JS error logs (message, category, page, app version, minified `line:col`), filterable by category + time window. - **Source-map de-obfuscation:** upload a `.map` from the tab and resolve any error's minified stack back to original file / line / column / symbol + a source snippet, choosing which map to apply. - Maps are held in **BFF memory only** (no backend storage): surfaced as *temporary*, LRU-evicted under a configurable budget (defaults 64 MiB/file, 512 MiB total), lost on restart. For durable provisioning, `.map` files can be **statically mounted** (a boot directory; `/app/sourcemaps` in the image) and reload automatically. - Resolution runs server-side in the Node BFF (`@jridgewell/trace-mapping`), so maps never reach the browser and their embedded source stays server-side. Upload/delete need `source-map:write`; viewing/resolving need `browser-errors:read`. **Known limits:** the agent reports a free-text `error.stack` + top-level `line/col` (populated only for the `JS` category) and no build fingerprint, so map↔build matching is operator-chosen (you pick the map; the resolved view names it). Stacks from V8/Gecko/JSC are parsed. Covers anything compiling to JS that ships a Source Map v3 (JS/TS/JSX/Vue/…); not inline/`eval`/no-build code or WASM. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
