v1.317.0
特徴
AJAXペイロードの検出とレポート
XMLHttpRequestおよびFetch APIコールのAJAXペイロードキャプチャのサポートを導入しました。有効にすると、Browserエージェントはリクエスト/レスポンスの本文、ヘッダー、およびクエリパラメーターをキャプチャし、GraphQL操作を自動的に検出して解析します。ペイロードキャプチャは、すべてのrequestsまたは失敗のみをモニターするように設定可能であり、組み込みのサイズ制限（属性あたり4KB）と機密データ保護のための難読化サポートを備えています。
新しいAjaxRequest属性
ペイロードキャプチャ - Browserエージェントは、AJAXコールのリクエストおよびレスポンスペイロードをキャプチャしてレポートできるようになり、ネットワークアクティビティとAPIインタラクションに関するより深いインサイトを提供します。
設定:ajax.capture_payloads設定オプションを使用してペイロードキャプチャを有効にします：
'all'- すべてのAJAX requestsのペイロードをキャプチャする'failures'- 失敗したrequests（HTTPエラー、ネットワークエラー、またはGraphQLエラー）のみをキャプチャするnone- ペイロードキャプチャを無効にする（デフォルト）
AjaxRequestイベントの新しい属性:AJAXペイロードがキャプチャされると、新しい属性がAjaxRequestイベントに自動的に含まれます：
requestQuery- URLクエリパラメーターrequestHeaders、responseHeaders- HTTPヘッダーrequestBody、responseBody- リクエストおよびレスポンスペイロード（テキストベースの形式のみ：JSON、XML、GraphQL、プレーンテキスト）
GraphQLの検出:GraphQLエラーが検出されると、新しい追加属性がAjaxRequestイベントに自動的に含まれます：
operationHasErrors- 操作がエラーを返したかどうかを示します
キャプチャされたすべてのデータは属性あたり4KBに自動的に切り捨てられ、機密情報の難読化パターンをサポートします。
イベントフィルターをサポートするための難読化の強化
難読化の動作は、eventFilterプロパティを使用して、イベントタイプのサブセットにのみ適用するように設定できるようになりました。このプロパティは、難読化ルールごとにイベントタイプ文字列の配列をサポートします。指定された場合、難読化ルールは、イベントタイプがeventFilter配列の項目のいずれかに一致する場合にのみ適用されます。下位互換性のため、設定ルールにeventFilterプロパティを指定しない場合、ルールはすべてのデータに適用されます。
バグ修正
切り捨てられたスタックトレースからbrowser_stack_hashを計算する
切り捨てられていないスタックトレースの代わりに、切り捨てられたスタックトレースからブラウザのスタックハッシュを計算します。この変更前は、JSEイベントの初回発生時のハーベストでは、スタックトレースが切り捨てられた場合、同じスタックトレースの将来のハーベストとは異なるブラウザのスタックハッシュを持つ可能性がありました。これにより、JavaScriptErrorイベントのエラーグループ化が改善されます。
content-lengthが欠落している場合、bodyからresponseBodySizeを取得する
フォールバックメカニズムの欠如と過度に制限的なfalsyチェックにより、AjaxRequestイベントがresponseSizeを0またはundefinedと不正確にレポートする問題に対処しました。content-lengthヘッダーが欠落している場合、FetchおよびXHR requestsのキャプチャされたペイロードからレスポンスサイズを計算するフォールバックメカニズムを導入しました。
セッションリプレイのインライン画像の処理にパッチを適用
セッションリプレイがライブDOMで画像を壊れたままにする可能性がある問題を修正しました。このバージョンでは、基盤となるrrwebバージョンはDOM上のライブ画像の操作を回避します。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
当社のブラウザサポートポリシーに従い、Browserエージェントのv1.317.0は、次のブラウザおよびバージョン範囲向けにビルドされ、テストされました：Chrome 139-149、Edge 139-149、Safari 18-26、およびFirefox 141-151。モバイルデバイス向けに、v1.317.0はAndroid OS 16および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
Features
Add ajaxRequest.id attribute
Adds a unique identifier to all AjaxRequest events to facilitate direct queries and drilling-down into data in NR1 UIs.
Improve PageViewTiming load timing capture
The load timing is now more reliably captured for pages, inheriting the idea from web-vital's onTTFB. Before, it occasionally missed loadEventEnd from nav entry from a browser race condition, particularly for larger/longer-loaded pages, which caused load to be 0.
Adjust timestamps for clock skew due to machine sleep
Certain linux and apple hardware can freeze the performance API clocks when entering deep sleep, which can cause inaccurate timestamps on New Relic events upon awakening. This introduces a new change which attempts to correct clock skew caused by frozen machines.
Automatically Detect MFE User Actions
Add support for automatic Micro Frontend (MFE) attribution of UserAction events via a data-nr-mfe-id data attribute. Previously, UserAction events were only ever captured globally by the container browser application. With this change, the agent now performs a parental chain lookup for elements associated with the action, identified by the data-nr-mfe-id attribute.
To associate UserAction events with a registered MFE, add a data-nr-mfe-id at the root DOM node controlled by your MFE package that matches the ID supplied to the register API.
Allow Session Replay to retry payloads
Payloads failed with retryable codes will be re-harvested by the agent. Further session replay data will not be collected until the harvest retries successfully.
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.314.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.314.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.313.1
バグ修正
MFEメソッドのメソッド名を修正する
Minified版になり、改善のために内部で追跡できなくなる可能性があったMFEメソッド名を修正しました。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
当社のブラウザサポートポリシーに従い、Browserエージェントのv1.313.1は、以下のブラウザおよびバージョン範囲向けに構築され、テストされています：Chrome 136～146、Edge 136～146、Safari 18～26、およびFirefox 138～148。モバイルデバイスの場合、v1.313.1はAndroid OS 16およびiOS Safari 18～26.2向けにビルドおよびテストされました。
v1.313.0
Features
Automatically Detect MFE Errors
Add support for automatic Micro Frontend (MFE) attribution of JavaScriptError events. Previously, JavaScriptError events were only ever captured globally by the container browser application. With this change, the agent cross-compares the stack trace of the thrown Error instance 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 stack trace of the thrown Error instance, that event will be attributed to the MFE instead of the container.
remove "withCredentials"
Remove all usage of withCredentials or credentials: 'include' from agent harvests, as cookies have not been used in the agent since before v1220.
Improve MicroFrontEndTiming heuristics
Improve the ability to detect script execution times for MFE, leading to more accurate timeToLoad metrics.
Report CSP violations as new events
Content Security Policy (CSP) violations bubbled up are now captured and reported as a new SecurityPolicyViolation event type to Page Insight consumer. They become query-able through NRQL.
Apply legal and compliance requirements to register API
Ensure the register API complies to company requirements before exposing for limited preview.
Bug fixes
Bad trace.lastTimestamp in Safari + back nav edge case
Fixes a race condition where Safari browser's back navigation (BFCache) could cause absolute timestamps to be recorded at the start of the session trace feature, resulting in an abnormal trace.lastTimestamp value and a mix of relative and absolute timestamps in a single payload.
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.313.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.313.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.312.1
Bug fixes
.at causes issues in older browsers
.at() is not being properly transpiled and causing initialization issues, switched to indexing.
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.312.1 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.312.1 was built and tested for Android OS 16 and iOS Safari 18-26.2.
v1.312.0
Features
Automatically Detect MFE Logs
Add support for automatic Micro Frontend (MFE) attribution of Log events. Previously, Log 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 given log method (such as console.log, console.info, etc.) 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 log method being triggered, that event will be attributed to the MFE instead of the container.
Automatically Detect MFE AJAX
Add support for automatic Micro Frontend (MFE) attribution of AjaxRequest events. Previously, AjaxRequest events were only ever captured globally by the container browser application. With this change, the agent cross-compares the call stack signature of the AJAX call 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 AJAX request being triggered, that event will be attributed to the MFE instead of the container.
Bug fixes
Session replays not working for Angular app running on Safari
Fixes an issue where session replays would fail to capture any recordings beyond an initial snapshot for Angular apps running on Safari.
Revert circular replacer
The circular replacer method applied to JSON.stringify operations was seen to cause lag in niche cases with deeply complex and nested objects emitted in quick succession such as in scroll event handlers. This method was revert back to a faster simpler operation to decrease performance bottlenecks.
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.312.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.312.0 was built and tested for Android OS 16 and iOS Safari 18-26.2.