We’ve hardened the Web SDK to be more compatible with 3rd party libraries, a response to discovering a previous incompatibility with the Bright Cove library.
Impacts now factor in more data when they determine a change.
XMLHttpRequestcalls during the regular course of it monitoring in order to capture performance & network errors and build better devtools. Out of the box we also detect and separate different graphql calls based on the
Check out the documentation here : LINK
We’ve reduced the amount of data necessary to recompute the impact of specific issues. As a result, users will benefit from a decreased load time for all new and existing issues.
In an effort to deliver what matters to you in a format that allows you to be most efficient, we’ve redesigned our homepage. Here, you will be able to see:
- Activity happening on your subscribed reports, issues or views.
- New issues in your subscribed views.
If an upload fails for an unforeseen reason, we gracefully retry when the system is in an idle state without overloading the client or the server machines.
We now cache all necessary metrics in the PlayerZero application, so realtime computation is focused on additional data, rather than the entire dataset as a whole. That means faster time to value, and less getting blocked on load screens.
We’ve doubled down on performance by optimizing regex & PII masking.
We’ve just enabled crosstab tracking on our recorder. That means events can now be tracked across different tabs for the same user. We’ve known since the start that a user’s story doesn’t always end in the tab it started in – crosstab tracking allows us to tell the story of a user instead of just a tab.
We’ve decreased time to value for our users by reducing the time between a user running into an issue and PlayerZero cataloging and classifying it. This allows us to improve the speed of our notifications – moving them closer to real time updates.