v1.317.0
특징
AJAX 페이로드 감지 및 보고
XMLHttpRequest 및 Fetch API 호출에 대한 AJAX 페이로드 캡처 지원을 도입합니다. 활성화되면 브라우저 에이전트는 GraphQL 작업의 자동 감지 및 구문 분석과 함께 요청/응답 본문, 헤더 및 쿼리 파라미터를 캡처합니다. 페이로드 캡처는 모든 requests 또는 실패만 모니터하도록 설정할 수 있으며, 민감한 데이터 보호를 위한 내장된 크기 제한(속성당 4KB) 및 난독화 지원이 제공됩니다.
새로운 AjaxRequest 속성
페이로드 캡처 ― 브라우저 에이전트는 이제 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가 누락된 경우 본문에서 responseBodySize 가져오기
대체 메커니즘의 부재와 지나치게 제한적인 falsy 검사로 인해 AjaxRequest 이벤트가 responseSize 을(를) 0 또는 undefined (으)로 부정확하게 보고하던 문제를 해결했습니다. content-length 헤더가 누락된 경우 Fetch 및 XHR requests에 대해 캡처된 페이로드에서 응답 크기를 계산하는 대체 메커니즘을 도입했습니다.
세션 리플레이를 위한 인라인 이미지 처리 패치
세션 리플레이가 라이브 DOM에 깨진 이미지를 남길 수 있는 문제를 수정합니다. 이 버전에서는 기본 rrweb 버전이 DOM의 라이브 이미지를 조작하지 않도록 합니다.
지지 성명
뉴렐릭은 에이전트를 정기적으로 업그레이드하여 최신 기능과 성능 이점을 얻을 것을 권장합니다. 이전 릴리스는 지원 종료 시점부터 더 이상 지원되지 않습니다. 출시일은 에이전트 버전의 원래 출판일을 반영합니다.
새로운 브라우저 에이전트 릴리스는 일정 기간 동안 작은 단계로 고객에게 출시됩니다. 이로 인해, 귀하의 계정에서 해당 릴리스에 접근할 수 있는 날짜가 원래 게시 날짜와 일치하지 않을 수 있습니다. 자세한 내용은 이 상태 대시보드를 참조하세요.
당사의 브라우저 지원 정책에 따라, 브라우저 에이전트 v1.317.0은 다음 브라우저 및 버전 범위에 대해 빌드되고 테스트되었습니다: Chrome 139-149, Edge 139-149, Safari 18-26 및 Firefox 141-151. 모바일 디바이스의 경우, v1.317.0은 안드로이드 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
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.
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.
v1.311.0
Features
agentIdentifier removal
Removed scoped references by agent identifier to simplify the agent architecture. All references are now stored directly within the agent reference, eliminating the need to blend agent references with scoped objects via lookup keys.
Attribute original page URL to all PageViewTiming nodes
Expanded pageUrl attribution to all timings, building on previous work for LCP. PageViewTiming events now report the original hard navigation URL for all node types, ensuring data consistency for SPA even if the URL changes before harvest.
improve MFE timing logic
Enhanced the agent's ability to identify the correct MFE script calling the register API. This improvement results in more accurate timing information for MFE environments.
Bug fixes
Enforce string IDs for new MFE registrations
Resolved an issue where non-string IDs caused errors during MFE entity synthesis. The agent now enforces string-based IDs and issues a warning if a different data type is provided.
Circular replacer removed reused objects from harvests
Fixed an issue where the internal stringify method removed shared pointers across harvest payloads, which occasionally caused missing params attributes on error harvests.
Update RegExp to prevent un-minimized webpack build issue
Replaced the $ character with its hexadecimal equivalent in regular expressions. This prevents Webpack from incorrectly replacing the character during the build process, which previously caused agent failures in unminimized builds.
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.311.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 18-26, and Firefox 137-147. For mobile devices, v1.311.0 was built and tested for Android OS 16 and iOS Safari 18-26.