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.
v1.288.0
특징
세션 만료 이후 세션 데이터 저장 방지
에이전트 세션이 만료되었음에도 불구하고 일부 세션 리플레이/세션 트레이스 데이터가 저장될 수 있는 극단적인 경우가 있을 수 있습니다. 측정, 로그를 추가하여 해당 발생을 감지하고 당분간 해당 이벤트 저장을 건너뜁니다.
InitialPageLoad 이벤트에 isFirstOfSession 속성을 도입합니다.
사용자 여정 지원을 돕기 위해 페이지가 새 세션의 첫 번째인 경우 초기 페이지 로드 종류의 BrowserInteraction 이벤트에 isFirstOfSession 맞춤 속성이 추가됩니다.
버그 수정
재생이 녹화를 중지하면 notified 재설정합니다.
세션 기록이 재개된 후 JavaScriptError 이벤트에 hasReplay 속성이 누락되는 문제를 해결합니다(예: 사용자가 다른 탭을 클릭하거나 탭이 유휴 상태가 된 후 다시 돌아온 경우).
로깅 중단 시 경쟁 조건 해결
에이전트가 이벤트 버퍼를 설정하기 전에 로깅 기능이 중단되면 오류가 발생할 수 있습니다. 이 문제는 메서드를 실행하기 전에 이벤트 버퍼의 존재 여부를 확인하여 해결되었습니다.
지지 성명
뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.
새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.
브라우저 지원 정책 에 따라, 브라우저 에이전트 v1.288.0은 다음 브라우저 및 버전 범위에 맞춰 빌드되고 테스트되었습니다: Chrome 124-134, Edge 124-134, Safari 17-17, Firefox 126-136. 모바일 장치의 경우 v1.288.0이 Android OS 15 및 iOS Safari 17-18.1에 대해 구축 및 테스트되었습니다.
v1.287.0
Features
Change architecture to help enable future Micro Front End support
Update the browser agent to support the future product decisions necessary to support micro front end architecture patterns from a single agent instance. This includes the addition of experimental APIs, intended to be used internally only to help support product development until future general availability (GA) is reached.
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.287.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.287.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.286.0
Features
Erase .api property on agent instance
The .api property of full and micro agents have been removed. The browser API methods are instead moved to the agent instance itself for ease of targeted access. This includes a minor fix of runtime loaderType for agents that are re-configured after load.
Reduce noise from mousemove events
There may be an edge case where a site performance can be impacted if the browser agent picked up mousemove events via addEventListener.
Handle duplicate agent APIs
Top-level interaction api calls are only responded to by the first exposed non-micro agent. This was changed to prevent issues for customers that run multiple agents together. The top-level interaction api should only be used to communicate with the main agent on the webpage. API calls on micro agents must instead be directly called on the respective micro agents.
Bug fixes
Patch newrelic event detail
There is an edge case where if there is a listener on the newrelic event (as described in the install docs) and any API call is invoked inside this listener, it will trigger an infinite loop.
Get string className for SVG elements
Change the nearestClass field for SVG elements to be a meaningful string name. The className of such elements is of type SVGAnimatedString and previously resulted in an empty object string.
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.286.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.286.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.285.0
Features
Decorate harvest requests with ht (hasTrace) param
Decorate with ht (hasTrace) query param for all harvest requests except for blobs and logs endpoints. This helps support searching for browser data with associated tracing data.
Inspection events
Adds inspection events that detail when various agent-related events occur. These events can be listened to on the event listener 'newrelic' string type. Events include agent initialization, agent fully loaded, event buffered, event harvested, and api calls.
Bug fixes
Session Replay text masking for whitespace
There is an edge case where whitespace was being masked, which interferes with the layout/styling in session replays.
Logging mode on session update
Fixes a typo in the session update handler for logging feature. The loggingMode which controls feature output will be correctly set after its session mode value is updated from another tab or window.
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.285.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.285.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.284.1
Bug fixes
Obtain FirstInteraction directly from performance API
To alleviate the potential performance impact of creating new performance observers to support legacy FirstInteraction timings, a change has been made to query the performance API directly for the presence of first-input data without the use of an observer at logical checkpoints.
Console error on some cross-origin requests without NR CAT header
XHR headers will be checked for the deprecated New Relic CAT header before calling getResponseHeader, which throws a console error if it does not exist for cross-origin requests.
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.284.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.284.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.284.0
Features
Remove FID, replace first interaction detection with INP
First Input Delay (FID) has been deprecated and replaced by Interaction To Next Paint (INP). PageViewTiming events for first interactions are preserved by detecting the first INP event and will no longer output value for the firstInputDelay attribute. For more info on PageViewTiming, see https://docs.newrelic.com/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details/. For more info on INP and the FID deprecation, see https://web.dev/articles/inp.
Bug fixes
Deduplicate Prefixes on Unhandled Promise Rejection Messages
Remove an issue that caused Unhandled Promise Rejection: prefixes on casted error messages to be duplicated if already supplied on rejection reason messages.
Upgrade rrweb to 18
Upgrade RRWeb dependency to version 18 to improve session replay performance.
bump web-vitals from 4.2.3 to 4.2.4
Bumps web-vitals from 4.2.3 to 4.2.4 to fix memory leak in registering new event listeners on every keydown and click (#554)
Guard against non-CSSStyleSheet when fixing sheets for replay
Nullish values in the global styleSheets API can break implementations with the weakMap object tracking their status, throwing an error similar to TypeError: Invalid value used in weak set at WeakSet.add.... This fix checks that the value is acceptable before adding.
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.284.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.284.0 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.283.2
Bug fixes
Add logging analytic metrics and fix browser performance metrics
Fix logging analytics metrics and centralize the metrics reporter for easier use
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.283.2 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.2 was built and tested for Android OS 15 and iOS Safari 17-18.1.
v1.283.1
Bug fixes
Removing websocket wrapping & SM
Removing websocket wrapping and metrics. WS instrumentation may be re-implemented behind a feature flag at a later 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.283.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 123-133, Edge 123-133, Safari 17-17, and Firefox 125-135. For mobile devices, v1.283.1 was built and tested for Android OS 15 and iOS Safari 17-18.1.