Browser agent release notesRSS

v1.324.0

View this release on GitHub → for the full technical changelog and build size information.

Features

Improve script matching in manifest

Micro frontends registered with a manifest now have every resource a manifest matcher matches counted toward their MicroFrontEndTiming data. Previously each manifest asset was consumed by its first matching resource, so a broad matcher such as a RegExp for hashed chunks (e.g. /catalog-chunk-[a-f0-9]+.js/) only contributed one chunk to totalWeight, renderBlocking and the fetch/execute timing window. All matching chunks, whether already loaded or loaded shortly after register(), now contribute. Separately, when the same script URL is referenced more than once (for example a duplicated <script> tag, typically re-served from the browser cache), the agent now keeps the timing from the first load instead of overwriting it, so a cached duplicate can no longer make fetch and execution timing look shorter than the real load.

Enable distributed tracing for registered Micro Frontends

Enables distributed tracing (DT) for registered Micro Frontends (MFEs): an AJAX call made by a registered MFE now correctly roots its trace at that MFE's own entity, giving visibility into an MFE's own backend calls for the first time.

Bug fixes

prevent runaway log harvests from inflated attribute size

Fixed a bug where a page that repeatedly overwrites a custom attribute could cause the agent to send a separate logs request for every logged message, flooding the network and exhausting browser resources. The agent now tracks custom attribute size accurately when values are overwritten, limits how often each feature can harvest early, and still sends large batches promptly so that no logs are dropped while doing so.

fix(jserrors): reset stack hash memory on session reset

see https://new-relic.atlassian.net/browse/NR-626097 for details Resend the full stack trace once after a session reset, instead of a hash the backend may no longer be able to resolve due to cache TTLs.

find iframe entity script timings at registration

Registered iframe entities now identify the script that called register() when they are created, instead of after the parent agent responds. Previously the lookup ran after the registration round trip, when the calling script was no longer on the call stack, so the entity's asset, type and fetch timings could be missing or attributed to the agent's own script.

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.

The following features are currently in limited preview and will not receive standard support:

• Micro frontend (MFE) monitoring via the register() API
• BrowserPerformance "resource" type events

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.324.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 144-154, Edge 144-154, Safari 18-27, and Firefox 146-156. For mobile devices, v1.324.0 was built and tested for Android OS 17 and iOS Safari 18-26.2.

v1.323.0

View this release on GitHub → for the full technical changelog and build size information.

Features

Harvest SR on switch from ERROR to FULL mode

Update agent to handle session replays the same way as session traces, and trigger a replay harvest when SR is switching from error to full mode.

Add internal adoption metrics for AJAX Payloads

Adds an internal metric measuring adoption of AJAX payload tracking for quality assurance and improvement purposes.

Bug fixes

fix(ajax): correct DT header timestamp to server time

Distributed tracing headers (traceparent/tracestate/newrelic) generated for AJAX requests now use the New Relic server-corrected timestamp when the agent's TimeKeeper has completed its RUM-based clock correction, rather than the browser's raw local clock value. This timestamp only affects the transport duration value a receiving backend APM agent computes for its own span -- it has no effect on any other browser telemetry.

Ensure timeKeeper readiness on Connector race condition

The new Connector in RUM v2 is patched to ready the TimeKeeper, critical to agent timestamp adjustments, under a minority-case race condition branch. This is behind the feature flag and should have no impact to any user right now.

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.

The following features are currently in limited preview and will not receive standard support:

• Micro frontend (MFE) monitoring via the register() API
• BrowserPerformance "resource" type events

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.323.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 143-153, Edge 142-152, Safari 18-27, and Firefox 145-155. For mobile devices, v1.323.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.322.0

Caractéristiques

Inclure l'API observer pour les événements SPV

Utilisez l'API ReportingObserver pour capturer les événements securitypolicyviolation survenus avant l'exécution du chargeur d'agent. En pratique, cela affecte principalement les navigateurs Chromium, car les configurations existantes et les bugs affectent la collecte de Firefox et Safari.

Manifeste MFE

Ajoute un manifest facultatif à l’API register() afin qu’un Micro Frontend puisse déclarer ses propres ressources connues (scripts, feuilles de style, images, polices), permettant à l’agent de lui attribuer avec précision les erreurs, les logs, les appels AJAX, les WebSockets, et les événements de timing des ressources, même pour les ressources chargées par un script autre que celui qui a appelé register(). Un timingMethod optionnel permet également à un manifeste d’élargir les fenêtres de récupération/exécution de MicroFrontEndTiming sur ses ressources déclarées.

Ajouter des avertissements de validation d’inscription

Émet des avertissements de débogage local si des problèmes évidents sont détectés depuis les cibles fournies vers l’API register.

Débogage

Mise à niveau de web-vitals de 4.2.4 vers 6.2.1 pour colmater une fuite d’écouteur

Mise à niveau de la bibliothèque web-vitals intégrée de 4.2.4 à 6.2.1, corrigeant une fuite illimitée d’écouteur document visibilitychange : web-vitals 4.x enregistre un écouteur permanent à chaque cycle de rapport INP, de sorte que les pages à longue durée de vie accumulent des centaines d’écouteurs. A également absorbé les modifications de l’API d’attribution v5/v6 auxquelles l’agent est exposé (le renommage LCPAttribution.element → target et les champs d’attribution INP/CLS nouvellement facultatifs) sans modification des noms d’attributs que l’agent émet.

Déclaration de soutien

New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront la fin de leur vie. Les dates de sortie reflètent la date de publication originale de la version de l'agent.

Les fonctionnalités suivantes sont actuellement en aperçu limité et ne recevront pas d’assistance standard :

• Monitoring des micro-frontends (MFE) via l’API register()
• Événements de type BrowserPerformance « resource »

Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce dashboard d'état pour plus d'informations.

Conformément à notre politique de prise en charge des navigateurs, la version v1.322.0 de l’agent Browser a été construite et testée pour ces navigateurs et plages de versions : Chrome 142-152, Edge 141-151, Safari 18-27 et Firefox 144-154. Pour les appareils mobiles, la v1.322.0 a été compilée et testée pour Android OS 16 et iOS Safari 18-26.2.

v1.321.0

Features

MicroFrontEndTiming attributes changes

MicroFrontEndTiming event attribute changes

Additions:

• registerUrl: The URL at the time the MFE was registered
• deregisterUrl: The URL at the time the MFE was deregistered or the page unloaded
• vitals.fcp.value: The value of the first contentful paint detected tied to the MFE DOM tree
• vitals.lcp.value: The value of the largest contentful paint detected tied to the MFE DOM tree
• vitals.cls.value: The value of the cumulative layout shift detected tied to the MFE DOM tree
• vitals.inp.value: The value of the interaction to next paint detected tied to the MFE DOM tree

Removals:

• pageUrl
• currentUrl

Add instrumentation to track races between tabs

Adds a supportability metric to track a race condition that occurs when another page runs at the same time with an updated session state.

improve v2 target standardization

Improves agent internals to provide an explicit reference for container agent targets while processing v2 MFE pathway data, rather than relying on side-effect driven undefined target assumptions.

Introduce v2 PageView & decouple connect service call

The old RUM request responsible for both retrieving app configurations and PageView generation is now split (temporarily under a feature flag). This makes the agent more resilient on problematic connect cycles or unsuccessful config retrieval, and the PageView event would no longer be the dependency blocking other events from harvesting.

Bug fixes

Ensure Session Replay's custom masker applies to non-inputs

Fixed an issue where the custom masker function was not applying to certain element types. The custom masker is applied to elements that are decorated with one of nr-umask CSS class or data-nr-unmask data attribute, allowing a node that would otherwise be masked to be overridden and its text contents exposed.

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

v1.320.1

Débogage

Évitez d’obfusquer les clés et les valeurs système réservées

Préserve toutes les clés ainsi que les valeurs système réservées pour les événements AjaxRequest et Page View Timing.

Appliquer une limite stricte à MFE FCP

Corrige un problème où les constantes vitales MFE pouvaient occasionnellement signaler des valeurs FCP/LCP hors limites (par exemple après le gel ou la suspension d'un onglet de navigateur) au lieu d'être abandonnées comme d'autres données obsolètes.

Déclaration de soutien

New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront la fin de leur vie. Les dates de sortie reflètent la date de publication originale de la version de l'agent.

Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce dashboard d'état pour plus d'informations.

Conformément à notre politique de prise en charge des navigateurs, la v1.320.1 de l'agent Browser a été conçue pour et testée sur les navigateurs et plages de versions suivants : Chrome 140-150, Edge 140-150, Safari 18-27 et Firefox 142-152. Pour les appareils mobiles, la v1.320.1 a été compilée et testée pour Android OS 16 et 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.