getsentry / getsentry/sentry-javascript

Improve Session Replay integration with server rendered HTML pages (MPAs)

オープン
#9,490 コメント 11 件 リアクション 1 件 担当者 0 名 GitHub で見る
Browser Improvement Replays
主要言語
TypeScript
スター
8.7k
フォーク
1.8k
平均マージ
1日 17時間
マージ済み PR(30日)
515

説明

We're working on onboarding for backend project to include browser support. Similar to how we have NextJS, Remix, we want to onboarding for Laravel, ASP.NET, Django, Express, Spring, etc to include a snippet to be added to their `html` template. Enabling an experience to a single framework such as NextJS:

I was talking to @mydea and a few ideas came up:

* Tracing end to end
* Release from trace baggage (to make it easier to onboard with the loader, uses same release version as backend)
* If exception happens on the backend, we want to replay to sample.
* Pass event_Id to the frontend so replay can send it. We could also define the `replay_id` on the backend so the error includes
* Could be done by setting the replay_id on the baggage given by the BE to the FE when rendering
* but for that to make sense we need the buffer to persist page loads
* Needs: remove minFlushDelay
* Keep last 30 seconds buffer for on error somehow?
* Shared worker?
* In the compression worker have an opt-in to store data in the worker in indexDB.

Also:
* https://github.com/getsentry/sentry-javascript/issues/9756

コントリビューションガイド

コントリビューションガイドを開く

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。