v1.257.0
Features
Session Replay preload optimizations
Optimize early load error detection to mitigate certain race conditions when transitioning from error mode to full mode.
Decorate errors with hasReplay individually
Change the error aggregation method to consider errors with a hasReplay flag separately to ensure timestamps are always correct. Decorate each aggregation set with hasReplay directly instead of a request-level query param
Bug fixes
Session replay preload without autoStart
In scenarios where SessionReplay was configured to not auto start and the user already has a replay recording from a previous page or after a page reload, calls to the start('session_replay')
API made too soon after agent initialization would be ignored.
JSEerrors harvest hasReplay decoration
In scenarios where the SessionReplay feature was preloaded but a recording was never started, errors happening on the page would be improperly decorated with the hasReplay
flag.
Agent class type declarations
Fixing incorrect type declarations for the constructor parameters of the Agent class.
Soft navigations memory leak on harvest
Address a couple scenarios of memory being not released by the soft navigation harvest cycle.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.257.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.
v1.256.1
Bug fixes
Revert "Generate PTID in Agent"
Revert a change causing Trace to begin harvest even when the rum flag given is 0
.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.256.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.
v1.256.0
Features
Generate PTID in Agent
Generate PTID in agent instead of in RUM response. This allows PageView events to be decorated with a page trace ID.
Allow unmasking elements with nr-unmask selectors
Add custom masking mechanism to allow unmasking elements with nr-unmask
class selectors and data-nr-unmask
data attribute selectors
Adjust Session Replay Error Tracking
Adjust when errors are decorated with session replay identifiers to more closely match actual recording data
Bug fixes
stabilize timestamp corrections
Ensure Session Replay timestamps are only ever adjusted once and fix correction factor to alleviate timeOrigin inconsistencies
Resume Page Focus Now Checks Session State
Check session state when resuming focus to an actively instrumented page. This ensures that stale sessions are caught before invoking other feature-level methods.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.256.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 114-123, Edge 114-123, Safari 16-17, and Firefox 115-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.
v1.255.0
Features
Adjust session replay timestamps to New Relic server time
Adjust all timestamps sent as session replay event nodes to represent New Relic server time for accuracy in querying against adjacent but separate events in the timeline such as errors, page views, and interactions.
Send CLS as timing node additionally
cumulativeLayoutShift
can now be queried for (with that as its timingName
) as its own PageViewTiming
event in New Relic. The additional attribution are a part of these events, and the values are more reflective of true end-session CLS scores.
Update agent to use new relic server time
Update the agent to use New Relic server time as the timestamp for harvested page action and error data.
Switch web vitals library to attribution build
Report extra attributes for each vital using web vital library's attribution build.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.255.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-123, Edge 113-122, Safari 16-17, and Firefox 114-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.
v1.254.1
Bug fixes
Server Timing - Remove reliance on performance API
Removing reliance on the browser resources API for the calculation of New Relic server time. On site with many resource requests, there was a small chance that the RUM network call would be flushed from the resources API cache before we could capture it and calculate server time.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.254.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-123, Edge 113-122, Safari 16-17, and Firefox 114-124. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-123 and iOS Safari 15.5-16.2.
v1.254.0
Features
Standardize all feature behavior to wait for RUM response
Force features to wait for entitlement checks from the rum call before processing buffered data.
maintain a harvestCount for use later with harvestId
Add a counter which increments after every harvest. This will be used in a future effort to curate a unique harvest ID for API paging purposes.
Add rum-response metadata handler
The initial connect call can now supply browser app metadata. This adds a handler to store and use that metadata for future harvests.
Calculate New Relic time in the agent
Migrating the process of time-stamping harvested data to the agent. The agent uses the date and time reported by the ingest pipeline during the RUM call as well as browser network and timing stats to derive a server time offset that can be applied to harvested data as event occur. This improves the ability to visualize the harvested data on a timeline within the New Relic UI.
Bug fixes
Remove webpack imports in npm package
Transitioning certain module imports so that the default import is for the npm version of the module instead of the cdn or webpack version. This should completely eliminate all references to webpack globals when using the npm package.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.254.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-122, Edge 113-122, Safari 16-17, and Firefox 114-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-122 and iOS Safari 15.5-16.2.
v1.253.0
Features
Soft Navigations trial
Introducing a lighter and simplified version of the existing spa feature that tracks soft navigations. This new feature still sends BrowserInteraction
events, but the duration and finishing of those interactions have been redefined. As a replacement, it ought to reduce complexity and integration issues around the existing spa and exhibit better and faster performance.
Apply deny list to ajax metrics
The ajax deny list has historically only applied to the collection of ajax events and not ajax metrics. With this feature, the deny list will also be applied to the collection and reporting of ajax timeslice metric data. If an ajax request matches an entry in the deny list, both events and metrics will be blocked from being collected in the agent. This feature will be behind a feature flag to assess impact before final complete rollout. Thanks to community member @Wrhector for contributing this feature.
Preload the session replay recorder when properly configured
Load the session replay recorder module before the page load when configured to do so. This will increase visibility for recordable data for customers who have opted in to the behavior.
Isolate observation context per agent
Initial implementation of an isolated observation context per agent running on the same page. This reduces the modification of instances of globals like events and instead each agent will track its own observation context internally.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.253.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 113-122, Edge 113-122, Safari 16-17, and Firefox 114-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-122 and iOS Safari 15.5-16.2.
v1.252.1
Bug fixes
Fix webpack imports in npm package
Fixing some import overrides in our NPM package build to prevent imports existing that include code reliant on webpack globals. This will resolve the error Uncaught ReferenceError: __webpack_require__ is not defined
when using the NPM package in a project that does not use webpack.
Page load after session timeouts don't start new session
When a session expires or becomes inactive while the user does not have the page open and they re-open the page, that is now treated as a new session.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.252.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 112-121, Edge 112-121, Safari 16-17, and Firefox 113-122. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-121 and iOS Safari 15.5-16.2.
v1.252.0
Features
Add types mappings for esm distribution
Adding typescript types mappings for the ESM distribution in the npm package.
Report config changes away from default state for UX improvement
Detect if the default config values have been altered at runtime. This is useful to evaluate what the reasonable defaults are across a customer base over time to provide a better UX.
Create more granular metrics about stylesheet fix success
Utilize a finer granularity when collecting success metrics on local stylesheet fixes for Session Replay compatibility.
Align browser reported uncaught syntax errors
Aligning the data reported for uncaught syntax errors across modern browsers. Chrome specifically fails to include the file name and line number in instances of SyntaxError. This could also cause issue in the New Relic error inbox where Chrome syntax errors were not being properly grouped.
Capture Internal Metrics for Session Replay Configurations
Capture supportability metrics sounding Session Replay configuration usage to improve user experiences around configuration of the agent's Session Replay feature.
Bug fixes
Add safe logic to snapshots
Safe-guarded a race condition where an asynchronous call to fix a stylesheet could trigger the agent to try to force a snapshot after it has already stopped recording due to a visibility change.
Fix adblock memory leak
Fixed memory leaks caused by request resolve failure (e.G. due to adblocker). Thanks to community member @Joe-Degler for contributing this fix.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.252.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 112-121, Edge 112-120, Safari 16-17, and Firefox 113-121. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-121 and iOS Safari 15.5-16.2.
v1.251.1
Bug fixes
Pass unload options to simultaneous harvests in session replay
Pass unload options to simultaneous harvests in session replay to allow all calls to utilize sendBeacon
when unloading.
Fix deferred session replay payloads
Force agent to send preloaded session replay payloads if present at load time.
Support statement
New Relic recommends that you upgrade the agent regularly to ensure that you're getting the latest features and performance benefits. Older releases will no longer be supported when they reach end-of-life. Release dates are reflective of the original publish date of the agent version.
New browser agent releases are rolled out to customers in small stages over a period of time. Because of this, the date the release becomes accessible to your account may not match the original publish date. Please see this status dashboard for more information.
Consistent with our browser support policy, v1.251.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 111-120, Edge 111-120, Safari 16-17, and Firefox 112-121. For mobile devices, v1.251.1 was built and tested for Android Chrome 100-120 and iOS Safari 15.5-16.2.