Browser agent release notesRSS

v1.322.0

Features

Include observer API for SPV events

Use the ReportingObserver API to catch securitypolicyviolation events that occurred prior to the agent loader execution. In practice, this mainly affects chromium browsers, as existing configs and bugs affect Firefox and Safari collection.

MFE Manifest

Adds an optional manifest to the register() API so a Micro Frontend can declare its own known assets (scripts, stylesheets, images, fonts), letting the agent accurately attribute errors, logs, AJAX calls, WebSockets, and resource-timing events to it — even for assets loaded by a script other than the one that called register(). An opt-in timingMethod also lets a manifest widen MicroFrontEndTiming fetch/execution windows across its declared assets.

Add registration validation warnings

Emits local debugging warnings if obvious issues are detected from supplied targets to the register API.

Bug fixes

Upgrade web-vitals from 4.2.4 to 6.2.1 to plug a listener leak

Upgraded the bundled web-vitals library from 4.2.4 to 6.2.1, fixing an unbounded document visibilitychange listener leak: web-vitals 4.x registers a permanent listener on every INP report cycle, so long-lived pages accumulate hundreds of listeners. Also absorbed the v5/v6 attribution API changes the agent is exposed to (the LCPAttribution.element → target rename and newly-optional INP/CLS attribution fields) with no change to the attribute names the agent emits.

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

v1.321.0

특징

MicroFrontEndTiming 속성 변경

MicroFrontEndTiming 이벤트 속성 변경

추가 사항:

• registerUrl: MFE가 등록된 시점의 URL
• deregisterUrl: MFE가 등록 취소되거나 페이지가 언로드된 시점의 URL
• vitals.fcp.value: MFE DOM 트리에 연결되어 감지된 최초 콘텐츠풀 페인트의 값
• vitals.lcp.value: MFE DOM 트리에 연결되어 감지된 최대 콘텐츠 풀 페인트의 값입니다.
• vitals.cls.value: MFE DOM 트리에 연결되어 감지된 누적 레이아웃 이동의 값
• vitals.inp.value: MFE DOM 트리에 연결되어 감지된 다음 페인트에 대한 상호작용의 값

제거:

• 페이지 URL
• 현재 URL

탭 간의 경합을 추적하기 위한 계측 추가

업데이트된 세션 상태로 다른 페이지가 동시에 실행될 때 발생하는 경쟁 조건을 추적하기 위해 지원 가능성 메트릭을 추가합니다.

v2 타겟 표준화 개선

부작용 기반의 정의되지 않은 타겟 가정에 의존하는 대신, v2 MFE 경로 데이터를 처리하는 동안 컨테이너 에이전트 타겟에 대한 명시적인 참조를 제공하도록 에이전트 내부를 개선합니다.

v2 PageView 도입 및 연결 서비스 호출 분리

앱 설정 검색과 PageView 생성 모두를 담당하던 기존 RUM 요청이 이제 분할되었습니다(기능 플래그 하에 임시로 적용됨). 이를 통해 에이전트는 문제가 있는 연결 주기나 실패한 설정 검색에 대해 더 강력한 복원력을 갖게 되며, PageView 이벤트는 더 이상 다른 이벤트의 수집을 차단하는 종속성이 되지 않습니다.

버그 수정

세션 리플레이의 사용자 지정 마스커가 입력이 아닌 요소에도 적용되도록 보장합니다.

사용자 지정 마스커 함수가 특정 요소 유형에 적용되지 않던 문제를 수정했습니다. 사용자 지정 마스커는 nr-umask CSS 클래스 또는 data-nr-unmask 데이터 속성 중 하나가 지정된 요소에 적용되어, 마스킹될 노드를 재정의하고 해당 텍스트 내용을 노출할 수 있도록 합니다.

지지 성명

뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.

새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.

당사의 브라우저 지원 정책에 따라, 브라우저 에이전트 v1.321.0은 다음 브라우저 및 버전 범위에 대해 빌드되고 테스트되었습니다: Chrome 141～151, Edge 141～151, Safari 18～27 및 Firefox 143～153. 모바일 디바이스의 경우, v1.321.0은 안드로이드 OS 16 및 iOS Safari 18～26.2용으로 빌드되고 테스트되었습니다.

v1.320.1

버그 수정

키 및 예약된 시스템 값을 난독화하지 마십시오.

AjaxRequest 및 Page View Timing 이벤트에 대한 예약된 시스템 값뿐만 아니라 모든 키를 보존합니다.

MFE FCP에 하드 캡을 적용하십시오

MFE 바이탈이 다른 오래된 데이터처럼 폐기되는 대신 때때로 범위를 벗어난 FCP/LCP 값을 보고할 수 있는 문제(예: 브라우저 탭 정지 또는 일시 중단 후)를 수정합니다.

지지 성명

뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.

새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.

브라우저 지원 정책에 따라, 브라우저 에이전트 v1.320.1은 다음 브라우저 및 버전 범위에 대해 빌드되고 테스트되었습니다: Chrome 140-150, Edge 140-150, Safari 18-27 및 Firefox 142-152. 모바일 디바이스의 경우, v1.320.1은 안드로이드 OS 16 및 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

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.