Our site deploys new builds almost weekly. We are now spending increasing amounts of time trying to track down BBR replay issues, specifically missing content that the BBR engine cannot retrieve.
In order to resolve these issues, we generally end up looking at the console, digging into logs, accessing localhost:38000 on the replay servers to look at resources and/or engaging a replay consultant to help us resolve replay issues.
This is unsustainable for a large, heterogeneous site like ours.
We need to be able to very quickly and easily identify what the root causes of a replay issue are in order to address them quickly and efficiently.
Please provide enhanced reporting/surfacing/analysis tools to simplify this process.
(RTV provides much better debug tools but does not support DOM capture. Porting these RTV diagnostics tools to BBR might be a good start.)