Browser agent release notesRSS

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

Recurso

Incluir API de observador para eventos SPV

Use a API ReportingObserver para capturar eventos securitypolicyviolation que ocorreram antes da execução do carregador do agente. Na prática, isso afeta principalmente os navegadores chromium, pois as configurações e os bugs existentes afetam a coleta do Firefox e do Safari.

Manifest do MFE

Adiciona um manifest opcional à API register() para que um Micro Frontend possa declarar seus próprios ativos conhecidos (scripts, folhas de estilo, imagens, fontes), permitindo que o agente atribua com precisão erros, logs, chamadas AJAX, WebSockets e eventos de tempo de recursos a ele — mesmo para ativos carregados por um script diferente daquele que chamou register(). Um timingMethod opcional também permite que um manifest amplie as janelas de busca/execução de MicroFrontEndTiming em seus ativos declarados.

Adicionar avisos de validação de registro

Emite avisos locais de depuração se problemas óbvios forem detectados a partir dos destinos fornecidos para a API de registro.

Correções de bugs

Atualize o web-vitals de 4.2.4 para 6.2.1 para corrigir um vazamento de listener

A biblioteca web-vitals incluída foi atualizada de 4.2.4 para 6.2.1, corrigindo um vazamento ilimitado de listener document visibilitychange: a web-vitals 4.x registra um listener permanente a cada ciclo de relatório INP, de modo que páginas de longa duração acumulam centenas de listeners. Também foram absorvidas as alterações da API de atribuição v5/v6 às quais o agente está exposto (a renomeação LCPAttribution.element → target e os campos de atribuição INP/CLS agora opcionais) sem alteração nos nomes de atributo que o agente emite.

Declaração de apoio

New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem ao fim de sua vida útil. As datas de lançamento refletem a data de publicação original da versão do agente.

Os seguintes recursos estão atualmente em visualização limitada e não receberão suporte padrão:

• Monitoramento de micro frontend (MFE) por meio da API register()
• Eventos do tipo BrowserPerformance “resource”

Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este dashboard de status para obter mais informações.

Em conformidade com nossa política de suporte ao navegador, a v1.322.0 do agente do Browser foi desenvolvida e testada para estes navegadores e faixas de versão: Chrome 142–152, Edge 141–151, Safari 18–27 e Firefox 144–154. Para dispositivos móveis, a v1.322.0 foi compilada e testada para Android OS 16 e 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

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

Recurso

Melhorias nos vitals do MFE

Implementa melhorias de qualidade de vida na coleta de tempos vitais do MFE.

• Se nenhum valor de FCP for observado em 10 segundos, encerre os observadores para economia de memória e controle de outlier.
• Decore as árvores DOM observadas com o ID da instância do MFE para facilitar a depuração e evitar a dupla instrumentação da mesma árvore DOM a partir de várias instâncias apontadas para o mesmo destino do MFE.

Detectar automaticamente Web Sockets do MFE

Adicionar suporte para atribuição automática de Micro Frontend (MFE) de eventos WebSocket. Anteriormente, os eventos WebSocket só eram capturados automaticamente de forma global pelo aplicativo de navegador do contêiner. Com essa alteração, o agente compara a assinatura da stack de chamadas do método WebSocket com a assinatura da stack de chamadas do módulo MFE que se registrou na API register. Se o arquivo responsável por se registrar no agente do browser for encontrado na assinatura da stack de chamadas do método WebSocket sendo acionado, esse evento será atribuído ao MFE em vez do contêiner.

Não ofuscar chaves de atributo

Não ofusque as chaves de atributo em nosso método addCustomAttributes para o serializador BEL. Essa alteração afeta os atributos nos eventos AjaxRequest, PageViewTiming e BrowserInteraction (apenas soft nav).

Correções de bugs

Evitar a captura de cargas AJAX do agente

Impede que o recurso AJAX capture_payloads capture as próprias requests de telemetria do agente (coletas para endpoints de beacon do NR).

Manter a carga Ajax fora de eventos não relacionados

Descarta a request AJAX capturada + informações de carga de eventos não relacionados (métricas de timeslice AJAX, trace da sessão) por meio de um objeto params compartilhado.

Declaração de apoio

New Relic recomenda que você atualize o agente regularmente para garantir que esteja obtendo os benefícios mais recentes de recursos e desempenho. Versões mais antigas não terão mais suporte quando chegarem ao fim de sua vida útil. As datas de lançamento refletem a data de publicação original da versão do agente.

Novos lançamentos de agente do browser são disponibilizados aos clientes em pequenas etapas ao longo de um período de tempo. Por esse motivo, a data em que o lançamento fica acessível à sua conta pode não corresponder à data de publicação original. Consulte este dashboard de status para obter mais informações.

De acordo com nossa política de suporte a navegadores, a versão v1.319.0 do agente do Browser foi criada e testada nesses navegadores e intervalos de versão: Chrome 139-149, Edge 139-149, Safari 18-27 e Firefox 142-152. Para dispositivos móveis, a v1.319.0 foi compilada e testada para Android OS 16 e iOS Safari 18-26.2.