Browser agent release notesRSS

v1.317.0

Features

Detect and report AJAX payloads

Introduces support of AJAX payload capture for XMLHttpRequest and Fetch API calls. When enabled, the browser agent will captures request/response bodies, headers, and query parameters, with automatic detection and parsing of GraphQL operations. Payload capture is configurable to monitor all requests or only failures, with built-in size limits (4KB per attribute) and obfuscation support for sensitive data protection.

New AjaxRequest Attributes

Payload Capture - The Browser Agent can now capture and report request and response payloads for AJAX calls, providing deeper insights into network activity and API interactions.

Configuration: Enable payload capture using the ajax.capture_payloads configuration option:

• 'all' - Capture payloads for all AJAX requests
• 'failures' - Capture only failed requests (HTTP errors, network errors, or GraphQL errors)
• none - Disable payload capture (default)

New Attributes on AjaxRequest Events: When AJAX payloads are captured, new attributes are automatically included on AjaxRequest events:

• requestQuery - URL query parameters
• requestHeaders, responseHeaders - HTTP headers
• requestBody, responseBody - Request and response payloads (text-based formats only: JSON, XML, GraphQL, plain text)

GraphQL Detection: When GraphQL errors are detected, a new additional attribute is automatically included on AjaxRequest events:

• operationHasErrors - Indicates if the operation returned errors

All captured data is automatically truncated to 4KB per attribute and supports obfuscation patterns for sensitive information.

Enhance obfuscation to support event filter

Obfuscation behavior can now be configured to apply only to a subset of event types, using the eventFilter property, which supports an array of event type strings per obfuscation rule. When supplied, the obfuscation rule will only be applied when the event type matches one of the items in the eventFilter array. For backwards compatibility, not supplying an eventFilter property on configuration rules will apply the rule to all data.

Bug fixes

Calculate browser_stack_hash from truncated stack trace

Calculate the browser stack hash off of the truncated stack trace instead of the non-truncated stack trace. Before this change, first-occurrence harvests of JSE events can have a different browser stack hash from future harvests of the same stack trace if it was truncated. This will improve error grouping of JavaScriptError events.

Get responseBodySize from body if content-length is missing

Addresses an issue where AjaxRequest events inaccurately reported a responseSize of 0 or undefined due to a lack of fallback mechanisms and overly restrictive falsy checks. Introduced a fallback mechanism that calculates response sizes from captured payloads for Fetch and XHR requests when the content-length header is missing.

Patch handling of inlining images for Session Replay

Fixes an issue where Session Replay may leave an image broken in the live DOM. In this version, the underlying rrweb version will avoid manipulating the live image on the DOM.

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.317.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 139-149, Edge 139-149, Safari 18-26, and Firefox 141-151. For mobile devices, v1.317.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.316.0

Features

Use app-namespaced keys for session

The browser agent now namespaces the session info to per browser app, using the combination of licenseKey and applicationID provided at startup. This means different apps sharing the same origin and browser localStorage will no longer share the same session, which was an accepted but not ideal collision, causing feature modes to bleed from one over to another for the duration of a session previously.

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.316.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.316.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.315.0

Features

Enhance SPA API to support targetPageLoad option

Allow the SPA API to target and work on the initialPageLoad type BrowserInteraction event. A new option is added to .interaction that now binds the returned handle to the initial page load interaction at any point in 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.315.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.315.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.314.0

Features

Add ajaxRequest.id attribute

Adds a unique identifier to all AjaxRequest events to facilitate direct queries and drilling-down into data in NR1 UIs.

Improve PageViewTiming load timing capture

The load timing is now more reliably captured for pages, inheriting the idea from web-vital's onTTFB. Before, it occasionally missed loadEventEnd from nav entry from a browser race condition, particularly for larger/longer-loaded pages, which caused load to be 0.

Adjust timestamps for clock skew due to machine sleep

Certain linux and apple hardware can freeze the performance API clocks when entering deep sleep, which can cause inaccurate timestamps on New Relic events upon awakening. This introduces a new change which attempts to correct clock skew caused by frozen machines.

Automatically Detect MFE User Actions

Add support for automatic Micro Frontend (MFE) attribution of UserAction events via a data-nr-mfe-id data attribute. Previously, UserAction events were only ever captured globally by the container browser application. With this change, the agent now performs a parental chain lookup for elements associated with the action, identified by the data-nr-mfe-id attribute.

To associate UserAction events with a registered MFE, add a data-nr-mfe-id at the root DOM node controlled by your MFE package that matches the ID supplied to the register API.

Allow Session Replay to retry payloads

Payloads failed with retryable codes will be re-harvested by the agent. Further session replay data will not be collected until the harvest retries successfully.

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.314.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.314.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.313.1

Bug fixes

Fix method names for MFE methods

Fixes MFE method names which could be minified and unable to be internally tracked for improvements.

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.313.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.313.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.313.0

Features

Automatically Detect MFE Errors

Add support for automatic Micro Frontend (MFE) attribution of JavaScriptError events. Previously, JavaScriptError events were only ever captured globally by the container browser application. With this change, the agent cross-compares the stack trace of the thrown Error instance to the call stack signature of the MFE module that registered with the register API. If the file that is responsible for registering with the browser agent is found in the stack trace of the thrown Error instance, that event will be attributed to the MFE instead of the container.

remove "withCredentials"

Remove all usage of withCredentials or credentials: 'include' from agent harvests, as cookies have not been used in the agent since before v1220.

Improve MicroFrontEndTiming heuristics

Improve the ability to detect script execution times for MFE, leading to more accurate timeToLoad metrics.

Report CSP violations as new events

Content Security Policy (CSP) violations bubbled up are now captured and reported as a new SecurityPolicyViolation event type to Page Insight consumer. They become query-able through NRQL.

Apply legal and compliance requirements to register API

Ensure the register API complies to company requirements before exposing for limited preview.

Bug fixes

Bad trace.lastTimestamp in Safari + back nav edge case

Fixes a race condition where Safari browser's back navigation (BFCache) could cause absolute timestamps to be recorded at the start of the session trace feature, resulting in an abnormal trace.lastTimestamp value and a mix of relative and absolute timestamps in a single payload.

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.313.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.313.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.312.1

Bug fixes

.at causes issues in older browsers

.at() is not being properly transpiled and causing initialization issues, switched to indexing.

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.312.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.312.0

Features

Automatically Detect MFE Logs

Add support for automatic Micro Frontend (MFE) attribution of Log events. Previously, Log events were only ever automatically captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the given log method (such as console.log, console.info, etc.) to the call stack signature of the MFE module that registered with the register API. If the file that is responsible for registering with the browser agent is found in the call stack signature of the log method being triggered, that event will be attributed to the MFE instead of the container.

Automatically Detect MFE AJAX

Add support for automatic Micro Frontend (MFE) attribution of AjaxRequest events. Previously, AjaxRequest events were only ever captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the AJAX call to the call stack signature of the MFE module that registered with the register API. If the file that is responsible for registering with the browser agent is found in the call stack signature of the AJAX request being triggered, that event will be attributed to the MFE instead of the container.

Bug fixes

Session replays not working for Angular app running on Safari

Fixes an issue where session replays would fail to capture any recordings beyond an initial snapshot for Angular apps running on Safari.

Revert circular replacer

The circular replacer method applied to JSON.stringify operations was seen to cause lag in niche cases with deeply complex and nested objects emitted in quick succession such as in scroll event handlers. This method was revert back to a faster simpler operation to decrease performance bottlenecks.

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.312.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.312.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.311.0

Features

agentIdentifier removal

Removed scoped references by agent identifier to simplify the agent architecture. All references are now stored directly within the agent reference, eliminating the need to blend agent references with scoped objects via lookup keys.

Attribute original page URL to all PageViewTiming nodes

Expanded pageUrl attribution to all timings, building on previous work for LCP. PageViewTiming events now report the original hard navigation URL for all node types, ensuring data consistency for SPA even if the URL changes before harvest.

improve MFE timing logic

Enhanced the agent's ability to identify the correct MFE script calling the register API. This improvement results in more accurate timing information for MFE environments.

Bug fixes

Enforce string IDs for new MFE registrations

Resolved an issue where non-string IDs caused errors during MFE entity synthesis. The agent now enforces string-based IDs and issues a warning if a different data type is provided.

Circular replacer removed reused objects from harvests

Fixed an issue where the internal stringify method removed shared pointers across harvest payloads, which occasionally caused missing params attributes on error harvests.

Update RegExp to prevent un-minimized webpack build issue

Replaced the $ character with its hexadecimal equivalent in regular expressions. This prevents Webpack from incorrectly replacing the character during the build process, which previously caused agent failures in unminimized builds.

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.311.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.311.0 was built and tested for Android OS 16 and iOS Safari 18-26.