Browser agent release notesRSS

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

特徴

websocketの初期化設定を追加

NREUMの初期設定にweb_socketsブロックを追加します。web_sockets.enabledをtrueに設定すると、Webソケット機能がオンになります。Webソケット機能はデフォルトで無効になっています。

MFEコアウェブバイタルの検出

MFEによって生成された場合のFCP、INP、CLS、およびLCPの内部検出メソッドを追加

エージェントの起動を改善

RUM呼び出しが正常に完了する前にエージェントの起動が中断される可能性があり、機能セッションモードがローカルストレージに保存される（該当する場合）シナリオのサポートを改善します。

サポートステートメント

New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。

新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。

当社のブラウザサポートポリシーに従い、Browserエージェントのv1.318.0は、以下のブラウザおよびバージョン範囲向けに構築され、テストされています：Chrome 139～149、Edge 139～149、Safari 18～26、およびFirefox 141～151。モバイルデバイスの場合、v1.318.0はAndroid OS 16およびiOS Safari 18～26.2向けに構築され、テストされています。

v1.317.0

Features

Detect and report AJAX payloads

Introduces support of AJAX payload capture for XMLHttpRequest and Fetch API calls. When enabled, the browser agent will captures request/response bodies, headers, and query parameters, with automatic detection and parsing of GraphQL operations. Payload capture is configurable to monitor all requests or only failures, with built-in size limits (4KB per attribute) and obfuscation support for sensitive data protection.

New AjaxRequest Attributes

Payload Capture - The Browser Agent can now capture and report request and response payloads for AJAX calls, providing deeper insights into network activity and API interactions.

Configuration: Enable payload capture using the ajax.capture_payloads configuration option:

• 'all' - Capture payloads for all AJAX requests
• 'failures' - Capture only failed requests (HTTP errors, network errors, or GraphQL errors)
• none - Disable payload capture (default)

New Attributes on AjaxRequest Events: When AJAX payloads are captured, new attributes are automatically included on AjaxRequest events:

• requestQuery - URL query parameters
• requestHeaders, responseHeaders - HTTP headers
• requestBody, responseBody - Request and response payloads (text-based formats only: JSON, XML, GraphQL, plain text)

GraphQL Detection: When GraphQL errors are detected, a new additional attribute is automatically included on AjaxRequest events:

• operationHasErrors - Indicates if the operation returned errors

All captured data is automatically truncated to 4KB per attribute and supports obfuscation patterns for sensitive information.

Enhance obfuscation to support event filter

Obfuscation behavior can now be configured to apply only to a subset of event types, using the eventFilter property, which supports an array of event type strings per obfuscation rule. When supplied, the obfuscation rule will only be applied when the event type matches one of the items in the eventFilter array. For backwards compatibility, not supplying an eventFilter property on configuration rules will apply the rule to all data.

Bug fixes

Calculate browser_stack_hash from truncated stack trace

Calculate the browser stack hash off of the truncated stack trace instead of the non-truncated stack trace. Before this change, first-occurrence harvests of JSE events can have a different browser stack hash from future harvests of the same stack trace if it was truncated. This will improve error grouping of JavaScriptError events.

Get responseBodySize from body if content-length is missing

Addresses an issue where AjaxRequest events inaccurately reported a responseSize of 0 or undefined due to a lack of fallback mechanisms and overly restrictive falsy checks. Introduced a fallback mechanism that calculates response sizes from captured payloads for Fetch and XHR requests when the content-length header is missing.

Patch handling of inlining images for Session Replay

Fixes an issue where Session Replay may leave an image broken in the live DOM. In this version, the underlying rrweb version will avoid manipulating the live image on the DOM.

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.317.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.317.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.316.0

Features

Use app-namespaced keys for session

The browser agent now namespaces the session info to per browser app, using the combination of licenseKey and applicationID provided at startup. This means different apps sharing the same origin and browser localStorage will no longer share the same session, which was an accepted but not ideal collision, causing feature modes to bleed from one over to another for the duration of a session previously.

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.316.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.316.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.315.0

Features

Enhance SPA API to support targetPageLoad option

Allow the SPA API to target and work on the initialPageLoad type BrowserInteraction event. A new option is added to .interaction that now binds the returned handle to the initial page load interaction at any point in time.

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.315.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 136-146, Edge 136-146, Safari 18-26, and Firefox 138-148. For mobile devices, v1.315.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.

v1.314.0

特徴

ajaxRequest.id属性を追加する

NR1 UIでの直接クエリとデータの掘り下げを容易にするために、すべてのAjaxRequestイベントに一意の識別子を追加します。

PageViewTimingのロードタイミング取得を改善

web-vitalのonTTFBからアイデアを継承し、ページのロードタイミングがより確実に取得されるようになりました。以前は、特にサイズの大きい/読み込みに時間がかかるページにおいて、ブラウザの競合状態によりナビゲーションエントリからのloadEventEndが欠落することが時折あり、その結果、ロードが0になっていました。

マシンのスリープによるクロックスキューに合わせてタイムスタンプを調整する

一部のLinuxおよびAppleハードウェアでは、ディープスリープ状態に入るとパフォーマンスAPIのクロックがフリーズすることがあり、その結果、スリープ解除時にNew Relicイベントのタイムスタンプが不正確になる可能性があります。これにより、フリーズしたマシンに起因するクロックスキューの修正を試みる新しい変更が導入されます。

MFEユーザーアクションを自動検出

data-nr-mfe-idデータ属性によるUserActionイベントの自動マイクロフロントエンド（MFE）アトリビューションのサポートを追加します。以前は、UserActionイベントはコンテナブラウザアプリケーションによってグローバルにのみキャプチャされていました。この変更により、エージェントは、data-nr-mfe-id属性によって識別される、アクションに関連付けられた要素の親チェーンの検索を実行するようになりました。

UserActionイベントを登録されたMFEに関連付けるには、register APIに提供されたIDと一致するdata-nr-mfe-idを、MFEパッケージによって制御されるルートDOMノードに追加します。

セッションリプレイがペイロードを再試行できるようにする

再試行可能なコードで失敗したペイロードは、エージェントによって再収集されます。収集の再試行が成功するまで、以降のセッションリプレイデータは収集されません。

サポートステートメント

New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。

新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。

当社のブラウザサポートポリシーに従い、Browserエージェントのv1.314.0は、以下のブラウザおよびバージョン範囲向けに構築され、テストされています：Chrome 136～146、Edge 136～146、Safari 18～26、およびFirefox 138～148。モバイルデバイスの場合、v1.314.0はAndroid OS 16およびiOS Safari 18～26.2向けにビルドおよびテストされました。