v1.324.1
View this release on GitHub → for the full technical changelog and build size information.
Bug fixes
correct hasMeta/hasSnapshot flags on session replay harvests
Fixed an issue where Session Replay harvests could incorrectly report hasMeta and hasSnapshot as false in their payload metadata even though the harvested data included valid snapshot nodes — most noticeable shortly after a session switched from error-only to full recording, or whenever the recorder restarted. This metadata was used downstream to determine whether a given replay chunk was self-sufficient (i.e. whether it could bootstrap a replay on its own), so an incorrect false could cause valid replay data to be mishandled.
Security fixes
bump fflate to 0.8.3
Addressed CVE-2026-45820 - unzipSync could enter an infinite loop when parsing malformed ZIP64 archives
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.1 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.1 was built and tested for Android OS 17 and iOS Safari 18-26.2.
v1.324.0
전체 기술 변경 로그 및 빌드 크기 정보는 GitHub에서 이 릴리스 보기 →를 확인해 주십시오.
특징
매니페스트에서 스크립트 일치를 개선합니다.
매니페스트에 등록된 마이크로 프런트엔드는 이제 매니페스트 매처와 일치하는 모든 리소스가 MicroFrontEndTiming 데이터에 반영됩니다. 이전에는 각 매니페스트 자산이 첫 번째로 일치하는 리소스에 의해 소비되었으므로, 해시된 청크에 대한 RegExp와 같은 광범위한 매처(예: /catalog-chunk-[a-f0-9]+.js/) totalWeight, renderBlocking 및 가져오기/실행 타이밍 창에 하나의 청크만 반영했습니다. 이미 로드되었거나 register() 직후에 로드되었는지 여부에 관계없이 일치하는 모든 청크가 이제 반영됩니다. 별도로, 동일한 스크립트 URL이 두 번 이상 참조되는 경우(예: 중복된 <script> 태그, 일반적으로 브라우저 캐시에서 다시 제공됨), 에이전트는 이제 덮어쓰는 대신 첫 번째 로드의 타이밍을 유지하므로 캐시된 중복이 더 이상 가져오기 및 실행 타이밍을 실제 로드보다 짧게 보이게 할 수 없습니다.
등록된 마이크로 프론트엔드에 대한 분산 추적을 활성화하십시오.
등록된 마이크로 프론트엔드(MFE)에 대한 분산 추적(DT)을 활성화합니다: 이제 등록된 MFE가 수행하는 AJAX 호출은 해당 MFE 자체 엔티티에 트레이스의 루트를 올바르게 지정하여, 처음으로 MFE 자체의 백앤드 호출에 대한 가시성을 제공합니다.
버그 수정
과도한 속성 크기로 인한 로그 수집 폭주를 방지합니다.
커스텀 속성을 반복적으로 덮어쓰는 페이지로 인해 에이전트가 모든 로그 메시지에 대해 별도의 로그 요청을 전송하여 네트워크를 폭주시키고 브라우저 리소스를 고갈시킬 수 있는 버그를 수정했습니다. 이제 에이전트는 값을 덮어쓸 때 커스텀 속성 크기를 정확하게 추적하고, 각 기능이 조기에 수집할 수 있는 빈도를 제한하며, 이 과정에서 로그가 누락되지 않도록 대규모 배치를 신속하게 전송합니다.
fix(jserrors): 세션 재설정 시 스택 해시 메모리를 재설정합니다.
자세한 내용은 https://new-relic.atlassian.net/browse/NR-626097을 참조하십시오. 캐시 TTL로 인해 백앤드가 더 이상 해석할 수 없는 해시 대신, 세션 재설정 후 전체 스택 추적을 한 번 다시 전송합니다.
등록 시 iframe 엔티티 스크립트 타이밍을 확인합니다.
등록된 iframe 엔티티는 이제 상위 에이전트가 응답한 후가 아니라 생성될 때 register()를 호출한 스크립트를 식별합니다. 이전에는 등록 왕복 이후에 조회가 실행되었으며, 이때 호출 스크립트는 더 이상 호출 스택에 없었기 때문에 엔티티의 자산, 유형 및 가져오기 타이밍이 누락되거나 에이전트 자체 스크립트의 속성으로 지정될 수 있었습니다.
지지 성명
뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.
다음 기능은 현재 제한된 프리뷰로 제공되며 표준 지원을 받지 않습니다:
- register() API 를통한 마이크로 프런트엔드(MFE) 모니터링
- BrowserPerformance "resource" 유형 이벤트
새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.
당사의 브라우저 지원 정책에 따라, 브라우저 에이전트 v1.324.0은 다음 브라우저 및 버전 범위에 대해 빌드되고 테스트되었습니다: Chrome 144~154, Edge 144~154, Safari 18~27 및 Firefox 146~156. 모바일 기기의 경우, v1.324.0은 안드로이드 OS 17 및 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
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
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
특징
MFE vitals에 합리적인 제한을 적용하는 기능을 개선합니다.
Register API의 마이크로 프런트엔드(MFE) 바이탈 추적에서 스크립트의 타이밍 상관관계가 오래된 후에도 재사용될 수 있어, 기본 스크립트를 다시 로드하지 않고 다시 마운트하는 MFE(예: 단일 페이지 애플리케이션)에 대해 First Contentful Paint(및 기타 바이탈)가 실제보다 최대 몇 초 더 느리게 잘못 보고되는 버그를 수정했습니다.
MFE iframe 지원 - 베타 액세스
iFrame에 캡슐화된 MFE 데이터를 캡처하기 위한 인터페이스를 추가합니다. 이는 실험적인 기능으로, 변경되거나 완전히 제거될 수 있으며 GA 상태에 도달할 때까지 운영 환경에서 사용해서는 안 됩니다.
버그 수정
자동 계측된 MFE 이벤트 중복 제거
마이크로 프런트엔드가 register() API에 여러 번 등록될 때 자동 계측된 이벤트(AJAX requests, JS 오류, 콘솔 로그, WebSocket 활동 등)의 중복 보고를 수정합니다. 이전에는 반복적으로 등록된 MFE 스크립트에서 발생하는 단일 자동 계측된 이벤트가 등록당 한 번씩 보고되었습니다 ― 이제 자동 감지된 이벤트는 동일한 기본 스크립트 및 동일한 등록된 MFE id로 확인될 때 실제 발생당 단일 보고서로 축소됩니다. 명시적인 API 기반 호출(.addPageAction(), .log(), .noticeError() 등) 및 MicroFrontEndTiming 이벤트는 의도한 대로 등록당 유지되며, 스크립트를 공유하는 별개의 MFE(예: 동일한 인라인 <script> 블록에서 등록된 두 개의 다른 MFE)는 계속해서 독립적으로 보고됩니다.
지지 성명
뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.
새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.
당사의 브라우저 지원 정책에 따라, 브라우저 에이전트 v1.320.0은 다음 브라우저 및 버전 범위에 대해 빌드되고 테스트되었습니다: Chrome 140-150, Edge 140-150, Safari 18-27 및 Firefox 142-152. 모바일 디바이스의 경우, v1.320.0은 안드로이드 OS 16 및 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.