v1.318.0
특징
웹소켓 초기화 설정 추가
NREUM 초기화 설정에 web_sockets 블록을 추가합니다. web_sockets.enabled 을(를) true (으)로 설정하면 웹소켓 기능이 켜집니다. 웹소켓 기능은 기본적으로 비활성화되어 있습니다.
MFE 코어 웹 바이탈 감지
MFE에 의해 생성될 때 FCP, INP, CLS 및 LCP에 대한 내부 감지 방법을 추가합니다
에이전트 시작 개선
RUM 호출이 성공적으로 완료되고 기능 세션 모드가 로컬 스토리지에 저장되기(해당하는 경우) 전에 에이전트 시작이 중단될 수 있는 시나리오에 대해 더 나은 지원을 제공합니다.
지지 성명
뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.
새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.
당사의 브라우저 지원 정책에 따라 브라우저 에이전트 v1.318.0은 다음 브라우저 및 버전 범위에 맞게 빌드되고 테스트되었습니다: Chrome 139-149, Edge 139-149, Safari 18-26 및 Firefox 141-151. 모바일 디바이스의 경우, v1.318.0은 안드로이드 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 parametersrequestHeaders,responseHeaders- HTTP headersrequestBody,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 로드 타이밍 캡처 개선
이제 웹 바이탈의 onTTFB에서 아이디어를 얻어 페이지의 로드 타이밍이 더 안정적으로 캡처됩니다. 이전에는 특히 더 크거나/더 오래 로드되는 페이지에서 브라우저 경합 조건으로 인해 nav 항목에서 loadEventEnd 이(가) 간혹 누락되어 로드가 0되는 원인이 되었습니다.
머신 절전 모드로 인한 클럭 스큐에 대해 타임스탬프 조정
특정 리눅스 및 애플 하드웨어는 절전 모드에 들어갈 때 성능 API 클럭을 멈추게 할 수 있으며, 이는 깨어날 때 뉴렐릭 이벤트에 부정확한 타임스탬프를 유발할 수 있습니다. 정지된 머신으로 인해 발생하는 클럭 스큐를 수정하기 위한 새로운 변경 사항을 도입합니다.
MFE 사용자 조치 자동 감지
data-nr-mfe-id 데이터 속성을 통한 UserAction 이벤트의 자동 마이크로 프론트엔드(MFE) 귀속에 대한 지원을 추가합니다. 이전에는, UserAction 이벤트가 컨테이너 브라우저 애플리케이션에 의해 전역적으로만 캡처되었습니다. 이 변경으로, 에이전트는 이제 data-nr-mfe-id 속성으로 식별되는 작업과 관련된 요소에 대해 상위 체인 조회를 수행합니다.
UserAction 이벤트를 등록된 MFE와 연결하려면, MFE 패키지가 제어하는 루트 DOM 노드에 register API에 제공된 ID와 일치하는 data-nr-mfe-id 을 추가하세요.
세션 리플레이가 페이로드를 재시도하도록 허용
재시도 가능한 코드로 실패한 페이로드는 에이전트에 의해 다시 수집됩니다. 수집 재시도가 성공할 때까지 추가 세션 리플레이 데이터는 수집되지 않습니다.
지지 성명
뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.
새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.
당사의 브라우저 지원 정책에 따라 브라우저 에이전트 v1.314.0은 다음 브라우저 및 버전 범위에 대해 빌드되고 테스트되었습니다: Chrome 136-146, Edge 136-146, Safari 18-26 및 Firefox 138-148. 모바일 기기의 경우, v1.314.0은 안드로이드 OS 16 및 iOS Safari 18-26.2용으로 빌드 및 테스트되었습니다.
v1.313.1
Bug fixes
Fix method names for MFE methods
Fixes MFE method names which could be minified and unable to be internally tracked for improvements.
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.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.313.1 was built and tested for Android OS 16 and 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.