v1.292.0
Features
Update BrowserInteraction and previousUrl definition
Update BrowserInteractions to use document.referrer for previousUrl values on initialPageLoad interactions instead of mirroring previousUrl and targetUrl. This enables better functionality for user journeys and provides more insight on page linkages.
Add more inspection events
Adds new inspection events to the agent. These events include the drain event, window lifecycle events such as navigate, load, DOMContentLoaded, and the session event which emits on changes to the agent's session state.
Bug fixes
Fix finished API timeSinceLoad value
Fixes an issue where the finished api was creating a timeSinceLoad value for PageAction data as the unix timestamp instead of a relative time value in seconds from the page origin.
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.292.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 127-137, Edge 127-137, Safari 17-18, and Firefox 128-138. For mobile devices, v1.292.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.
v1.291.1
Bug fixes
Prevent ST from holding onto Event refs in memory when aborted
Releases the Event entries the agent hold onto in Trace after it has aborted. This addresses a known case of memory leak caused by continuing to add those references to a Set that is never cleared.
Clean BrowserPerformance entryName for resources
The entryName attribute of resource type BrowserPerformance events will now have a cleaner URL, removing the hash fragment from reported URLs.
Add safeguards for addToTrace
Events created with addToTrace API, which have an invalid UNIX timestamp, emit a warning and return without creating the event.
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.291.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-18, and Firefox 128-138. For mobile devices, v1.291.1 was built and tested for Android OS 16 and iOS Safari 17-18.1.
v1.291.0
Features
Create the measure API
Adds the measure API to the newrelic global object. This API allows generating new BrowserPerformance data even if auto-detection of marks and measures is not enabled.
Bug fixes
Fix race between end of session and features aborting
Fix an issue where features would race with the session manager when a session ends. This required a check for session timings to match a given session and could create a state where a new session created from a pre-existing session would trigger a partial replay or no replay, and prevent the agent from sending trace data with a given replay.
Harvest first session trace payload immediately
For better consistency, implemented old behavior where the first ST payload is harvested immediately when the page loads. This helps ensure cases where replays are harvested but traces are not happen less frequently.
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.291.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 126-136, Edge 126-136, Safari 17-17, and Firefox 128-138. For mobile devices, v1.291.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.
v1.290.1
バグ修正
サイレント設定ゲッターの harvestCount メッセージのみ
エージェントがランタイムharvestCountを上書きしようとしたことによる警告は適切に抑制されます。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
弊社のブラウザ サポート ポリシーに従い、 Browserの v1.290.1 は、 Chrome 126 ～ 136、Edge 126 ～ 136、Safari 17 ～ 17、Firefox 128 ～ 138 のブラウザとバージョン範囲向けに構築され、テストされました。 モバイル デバイスの場合、v1.290.1 は Android OS 16 および iOS Safari 17-18.1 用に構築およびテストされました。
v1.290.0
Features
Bundler tools exports
An optional Webpack splitChunks cacheGroup matcher is now available for users who build the agent via NPM. This matcher enables de-duplication and merging of the agent's lazy-loaded JavaScript into a single chunk. This single chunk loads post-page render, consistent with the behavior of our pre-built agent for APM and copy/paste implementations.
Set UserAction currentUrl before aggregation end
Set currentUrl on the first event of a user action instead of at the end of aggregation.
Improve lazy-loading optimization
Optimize our pattern to ensure that code-bundlers such as webpack can more effectively tree-shake the output to only include the relevant files needed to run the agent. This specifically helps reduce the bundle size, reduce the amount of lazy files generated, and streamlines "custom" agent builds used with NPM.
API Code Splitting
Split the API method definitions per feature instead of a single file shared across all loader types. This allows each loader to only instantiate the necessary APIs for the features included, and reduce overall bundle size for the "Lite" build as well as custom-built agents with NPM. A shell will still exist for non-initialized APIs to prevent errors from throwing on APIs used without the needed features.
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.290.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.290.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.
v1.289.0
特徴
エージェント設定キャッシュとゲッター/セッターを削除する
内部設定ユーティリティ機能を削除します。 エージェントの機能に影響はないと考えられます。このコーディング スタイルの変更によりビルド サイズが削減されました。
サポートステートメント
New Relic では、最新の機能とパフォーマンス上のメリットを確実に得られるよう、エージェントを定期的にアップグレードすることをお勧めします。古いリリースはサポート終了になるとサポートされなくなります。リリース日は、エージェント バージョンの元の公開日を反映します。
新しいブラウザエージェントのリリースは、一定期間にわたって小さな段階で顧客に展開されます。 このため、リリースがアカウントでアクセス可能になる日付は、元の公開日と一致しない可能性があります。詳細については、このステータス ダッシュボードをご覧ください。
弊社のブラウザ サポート ポリシーに従い、 Browserの v1.289.0 は、 Chrome 125 ～ 135、Edge 125 ～ 135、Safari 17 ～ 17、Firefox 127 ～ 137 のブラウザとバージョン範囲向けに構築され、テストされました。 モバイル デバイスの場合、v1.289.0 は Android OS 16 および iOS Safari 17-18.1 用に構築およびテストされました。
v1.288.1
Bug fixes
Ensure event buffer always exists
Ensure event buffers always exist to prevent race conditions between agent life-cycles and data storage.
Call handle directly for submitting SM
This fixes a bad reference to a parent function that is not accessible.
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.288.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 125-135, Edge 125-135, Safari 17-17, and Firefox 127-137. For mobile devices, v1.288.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.288.0
Features
Prevent storing session data past session expiry
There may be edge cases where some Session Replay/Session Trace data could be stored even though the agent session has expired. Add instrumentation to detect such occurrences and skip storing these events for the time being.
Introduce isFirstOfSession attribute on InitialPageLoad events
To help support User Journeys, the isFirstOfSession custom attribute will be added to BrowserInteraction events of initial page load kind if the page is the first of a new session.
Bug fixes
Reset notified when replay stops recording
Resolves an issue where JavaScriptError events would be missing the hasReplay attribute after session recording is resumed (for example, from user clicking on another tab/tab going idle and then coming back to it).
Solve race condition in logging abort
If the logging feature aborted before the agent had set up the event buffer, it could throw errors. This was addressed by checking for the presence of the event buffer before running methods against it.
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.288.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 124-134, Edge 124-134, Safari 17-17, and Firefox 126-136. For mobile devices, v1.288.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.