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
Features
Add websocket init config
Adds web_sockets block to NREUM init configuration. Setting web_sockets.enabled to true turns on the web sockets feature. The web sockets feature is disabled by default.
MFE core web-vitals detection
Add internal detection methods for FCP, INP, CLS, and LCP when spawned by a MFE
Improve agent startup
Provide better support for scenarios where agent startup can be interrupted before RUM call completes successfully and feature session modes are saved into local storage (where applicable).
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.318.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.318.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.317.0
Característica
Detectar y reportar cargas AJAX
Introduce soporte para la captura de carga AJAX para llamadas API de XMLHttpRequest y Fetch. Cuando está habilitado, el agente del browser capturará los cuerpos de request/respuesta, los encabezados y los parámetros de consulta, con detección y análisis automáticos de las operaciones de GraphQL. La captura de carga es configurable para monitorear todos los requests o solo las fallas, con límites de tamaño incorporados (4KB por atributo) y soporte de ofuscación para la protección de datos confidenciales.
Nuevos atributos de AjaxRequest
Captura de carga - el agente del browser ahora puede capturar y reportar las cargas de request y respuesta para las llamadas AJAX, lo que proporciona información valiosa más profunda sobre la actividad de la red y las interacciones de la API.
Configuración: Habilite la captura de carga usando la opción de configuración ajax.capture_payloads:
'all'- Capturar cargas para todos los requests AJAX'failures'- Capturar solo los requests fallidos (errores HTTP, errores de red o errores de GraphQL)none- Deshabilitar la captura de carga (predeterminado)
Nuevos atributos en los eventos AjaxRequest: cuando se capturan las cargas de AJAX, se incluyen automáticamente nuevos atributos en los eventos AjaxRequest:
requestQuery- Parámetros de consulta de URLrequestHeaders,responseHeaders- Encabezados HTTPrequestBody,responseBody- Cargas de request y respuesta (solo formatos basados en texto: JSON, XML, GraphQL, texto sin formato)
Detección de GraphQL: Cuando se detectan errores de GraphQL, se incluye automáticamente un nuevo atributo adicional en los eventos de AjaxRequest:
operationHasErrors- Indica si la operación devolvió errores
Todos los datos capturados se truncan automáticamente a 4KB por atributo y admiten patrones de ofuscación para la información confidencial.
Mejorar la ofuscación para admitir el filtro de eventos
El comportamiento de ofuscación ahora se puede configurar para que se aplique solo a un subconjunto de tipos de eventos, usando la propiedad eventFilter, que admite una matriz de cadenas de tipos de eventos por regla de ofuscación. Cuando se proporciona, la regla de ofuscación solo se aplicará cuando el tipo de evento coincida con uno de los elementos de la matriz eventFilter. Para mantener la compatibilidad con versiones anteriores, si no se proporciona una propiedad eventFilter en las reglas de configuración, la regla se aplicará a todos los datos.
Corrección de errores
Calcular browser_stack_hash a partir del rastreo del stack truncado
Calcular el hash del stack del browser a partir del rastreo del stack truncado en lugar del rastreo del stack no truncado. Antes de este cambio, las recolecciones de primera aparición de eventos JSE podían tener un hash del stack del browser diferente de las recolecciones futuras del mismo rastreo del stack si se truncaba. Esto mejorará la agrupación de errores de los eventos JavaScriptError.
Obtener responseBodySize del cuerpo si falta content-length
Aborda un problema en el que los eventos AjaxRequest reportaban de manera inexacta un responseSize de 0 o undefined debido a la falta de mecanismos de respaldo y comprobaciones falsy demasiado restrictivas. Se introdujo un mecanismo de respaldo que calcula los tamaños de respuesta a partir de las cargas capturadas para los requests Fetch y XHR cuando falta el encabezado content-length.
Parche para el manejo de imágenes en línea para Session Replay
Soluciona un problema por el cual Session Replay podía dejar una imagen rota en el DOM en vivo. En esta versión, la versión subyacente de rrweb evitará manipular la imagen en vivo en el DOM.
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.317.0 del agente de 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.317.0 se compiló y probó para Android OS 16 e 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.