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
特徴
SPVイベント用のオブザーバーAPIを含める
エージェントローダーの実行前に発生したsecuritypolicyviolationイベントをキャッチするには、ReportingObserver APIを使用してください。実際には、既存の設定やバグがFirefoxおよびSafariの収集に影響を与えるため、これは主にChromiumブラウザーに影響します。
MFEマニフェスト
マイクロフロントエンドが自身の既知のアセット（スクリプト、スタイルシート、画像、フォント）を宣言できるように、オプションのmanifestをregister() APIに追加します。これにより、エージェントはエラー、ログ、AJAX呼び出し、WebSocket、およびリソース・タイミング・イベントをそれに正確に属性付けることができます — register()を呼び出したスクリプト以外のスクリプトによってロードされたアセットであっても。また、オプトインのtimingMethodにより、マニフェストは宣言されたアセット全体でMicroFrontEndTimingのフェッチ/実行ウィンドウを拡大できます。
登録検証の警告を追加
登録APIに提供されたターゲットから明らかな問題が検出された場合、ローカルデバッグ警告を発行します。
バグ修正
リスナーのリークを修正するため、web-vitalsを4.2.4から6.2.1にアップグレードしてください。
バンドルされているweb-vitalsライブラリを4.2.4から6.2.1にアップグレードし、無制限のdocument visibilitychangeリスナーのリークを修正しました：web-vitals 4.xはINPレポートサイクルごとに永続的なリスナーを登録するため、長時間開かれているページでは数百のリスナーが蓄積されます。また、エージェントが出力する属性名に変更を加えることなく、エージェントが影響を受けるv5/v6アトリビューションAPIの変更（LCPAttribution.element → target の名前変更、および新たにオプションとなったINP/CLSアトリビューションフィールド）を取り込みました。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
以下の機能は現在リミテッドプレビューであり、標準サポートは提供されません：
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
当社のブラウザサポートポリシーに従い、Browserエージェントのv1.322.0は、以下のブラウザおよびバージョン範囲向けに構築され、テストされました：Chrome 142～152、Edge 141～151、Safari 18～27、およびFirefox 144～154。モバイルデバイスについては、v1.322.0はAndroid OS 16およびiOS Safari 18～26.2向けに構築され、テストされました。
v1.321.0
特徴
MicroFrontEndTiming属性の変更
MicroFrontEndTimingイベント属性の変更
追加：
- registerUrl：MFEが登録された時点のURL
- deregisterUrl：MFEが登録解除された時点、またはページがアンロードされた時点のURL
- vitals.fcp.value：MFE DOMツリーに関連付けられて検出されたFirst Contentful Paintの値
- vitals.lcp.value：MFE DOMツリーに関連付けられて検出されたLargest Contentful Paintの値
- vitals.cls.value：MFE DOMツリーに関連付けられて検出されたCumulative Layout Shiftの値
- vitals.inp.value：MFE DOMツリーに関連付けられて検出された、インタラクションから次の描画までの値
削除：
- ページURL
- 現在のURL
タブ間の競合を追跡する計装を追加します。
更新されたセッション状態で別のページが同時に実行されたときに発生する競合状態を追跡するための、サポートアビリティメトリクスを追加します。
v2ターゲットの標準化を改善
v2 MFEパスウェイデータの処理中に、副作用主導の未定義のターゲットの仮定に依存するのではなく、コンテナエージェントのターゲットに対する明示的な参照を提供するように、エージェントの内部を改善します。
v2 PageViewを導入 & 接続サービス呼び出しを分離します。
アプリの設定の取得とPageViewの生成の両方を担当していた古いRUMリクエストは、分割されました（一時的に機能フラグの下にあります）。これにより、問題のある接続サイクルや設定の取得の失敗に対してエージェントの回復力が高まり、PageViewイベントが他のイベントの収集をブロックする依存関係ではなくなります。
バグ修正
セッションリプレイのカスタムマスカーが入力以外の要素に適用されることを確認します。
カスタムマスカー機能が特定の要素タイプに適用されない問題を修正しました。カスタムマスカーは、nr-umask CSSクラスまたはdata-nr-unmaskデータ属性のいずれかで装飾された要素に適用され、マスクされるはずのノードをオーバーライドして、そのテキストコンテンツを公開できるようにします。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
当社のブラウザサポートポリシーに従い、Browserエージェントのv1.321.0は、これらのブラウザとバージョン範囲向けにビルドされ、テストされました：Chrome 141～151、Edge 141～151、Safari 18～27、およびFirefox 143～153。モバイルデバイスの場合、v1.321.0はAndroid OS 16および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
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.