v1.320.1
Bug fixes
Avoid obfuscating keys and reserved system vals
Preserves all keys as well as reserved system values for AjaxRequest and Page View Timing events.
Apply hard cap to MFE FCP
Fixes an issue where MFE vitals could occasionally report out of bounds FCP/LCP values (e.g. after a browser tab freeze or suspend) instead of being dropped like other stale data.
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.320.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 140-150, Edge 140-150, Safari 18-27, and Firefox 142-152. For mobile devices, v1.320.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.320.0
Features
Improve ability to apply reasonable caps to MFE vitals
Fixed a bug in the Register API's micro-frontend (MFE) vitals tracking where a script's timing correlation could be reused after it went stale, causing First Contentful Paint (and other vitals) to be misreported as up to several seconds slower than they actually were for MFEs that remount without their underlying script reloading (e.g. in single-page applications).
MFE iframe support - Beta Access
Adds an interface for capturing MFE data encapsulated in an iFrame. This is experimental, is subject to change or total removal and should not be used in a production environment until GA status has been reached
Bug fixes
Deduplicate auto-instrumented MFE events
Fixes duplicate reporting of auto-instrumented events (AJAX requests, JS errors, console logs, WebSocket activity etc.) when a micro-frontend is registered with the register() API multiple times. Previously, a single auto-instrumented event originating from a repeatedly-registered MFE script would be reported once per registration — Auto-detected events are now collapsed to a single report per real occurrence when they resolve to the same underlying script and the same registered MFE id. Explicit API-driven calls (.addPageAction(), .log(), .noticeError(), etc.) and MicroFrontEndTiming events remain per-registration, as intended, and distinct MFEs that happen to share a script (e.g. two different MFEs registered from the same inline <script> block) continue to be reported independently.
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.320.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 140-150, Edge 140-150, Safari 18-27, and Firefox 142-152. For mobile devices, v1.320.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.319.0
Features
MFE vitals improvements
Implement quality of life improvements on the collection of MFE vital timings.
- If no FCP value is observed within 10 seconds, shut down observers for memory saving and outlier control.
- Decorate observed DOM trees with the MFE instance ID to facilitate debugging and prevent double-instrumentation of the same DOM tree from multiple instances pointed at the same MFE target.
Automatically Detect MFE Web Sockets
Add support for automatic Micro Frontend (MFE) attribution of WebSocket events. Previously, WebSocket 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 WebSocket method 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 WebSocket method being triggered, that event will be attributed to the MFE instead of the container.
Do not obfuscate attribute keys
Do not obfuscate attribute keys in our addCustomAttributes method for the BEL serializer. This change affects attributes in AjaxRequest, PageViewTiming, and BrowserInteraction (soft nav only) events.
Bug fixes
Avoid capturing agent AJAX payloads
Prevent the AJAX capture_payloads feature from capturing the agent's own telemetry requests (harvests to NR beacon endpoints).
Keep Ajax payload out of unrelated events
Drops captured AJAX request + payload info from unrelated events (AJAX timeslice metrics, session trace) via a shared params object.
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.319.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 139-149, Edge 139-149, Safari 18-27, and Firefox 142-152. For mobile devices, v1.319.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.318.0
Característica
Agregar configuración de inicio de websocket
Agrega el bloque web_sockets a la configuración de inicio de NREUM. Establecer web_sockets.enabled en true activa la característica de web sockets. La característica de web sockets está deshabilitada de forma predeterminada.
Detección de Métricas web principales de MFE
Agregar métodos de detección interna para FCP, INP, CLS y LCP cuando son generados por un MFE
Mejora el inicio del agente
Proporciona un mejor soporte para escenarios donde el inicio del agente puede interrumpirse antes de que la llamada de RUM se complete con éxito y los modos de sesión de la característica se guarden en el almacenamiento local (donde corresponda).
Declaración de apoyo
New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen al final de su vida útil. Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente.
Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este dashboard de estado para obtener más información.
De acuerdo con nuestra política de compatibilidad de navegadores, la v1.318.0 del agente del browser se creó y probó para estos navegadores y rangos de versiones: Chrome 139-149, Edge 139-149, Safari 18-26 y Firefox 141-151. Para dispositivos móviles, la v1.318.0 se compiló y probó para Android OS 16 e iOS Safari 18-26.2.
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 parametersrequestHeaders,responseHeaders- HTTP headersrequestBody,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
Característica
Mejorar la API de SPA para admitir la opción targetPageLoad
Permitir que la API de SPA tenga como objetivo y trabaje en el evento BrowserInteraction de tipo initialPageLoad. Se agrega una nueva opción a .interaction que ahora vincula el identificador devuelto a la interacción de carga inicial de la página en cualquier momento.
Declaración de apoyo
New Relic recomienda que actualices el agente periódicamente para garantizar que obtengas las últimas características y beneficios de rendimiento. Las versiones anteriores ya no recibirán soporte cuando lleguen al final de su vida útil. Las fechas de lanzamiento reflejan la fecha de publicación original de la versión del agente.
Las nuevas versiones del agente del browser se lanzan a los clientes en pequeñas etapas a lo largo de un periodo de tiempo. Debido a esto, la fecha en que el lanzamiento esté disponible en su cuenta puede no coincidir con la fecha de publicación original. Consulte este dashboard de estado para obtener más información.
De acuerdo con nuestra política de compatibilidad de navegadores, la versión 1.315.0 del agente de Browser se creó y probó para estos navegadores y rangos de versiones: Chrome 136-146, Edge 136-146, Safari 18-26 y Firefox 138-148. Para dispositivos móviles, la v1.315.0 se compiló y probó para Android OS 16 e 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.