Browser agent release notesRSS

v1.317.0

Caractéristiques

Détecter et signaler les charges AJAX

Introduit la prise en charge de la capture de charge AJAX pour les appels d’API XMLHttpRequest et Fetch. Lorsqu’il est activé, l’agent de navigateur capture les corps de requête/réponse, les en-têtes et les paramètres de requête, avec détection et analyse automatiques des opérations GraphQL. La capture de charge est configurable pour monitorer toutes les requests ou uniquement les échecs, avec des limites de taille intégrées (4 Ko par attribut) et la prise en charge de l’obfuscation pour la protection des données sensibles.

Nouveaux attributs AjaxRequest

Capture de charge – L'agent Browser peut désormais capturer et signaler les charges de requête et de réponse pour les appels AJAX, fournissant des informations détaillées plus approfondies sur l'activité du réseau et les interactions d'API.

Configuration : Activer la capture de charge à l'aide de l'option de configuration ajax.capture_payloads :

• 'all' - Capturer la charge pour toutes les requests AJAX
• 'failures' – Capturer uniquement les requests ayant échoué (erreurs HTTP, erreurs réseau ou erreurs GraphQL)
• none - Désactiver la capture de charge (par défaut)

Nouveaux attributs sur les événements AjaxRequest : lorsque les charges AJAX sont capturées, de nouveaux attributs sont automatiquement inclus sur les événements AjaxRequest :

• requestQuery - Paramètres de requête d’URL
• requestHeaders, responseHeaders - En-têtes HTTP
• requestBody, responseBody – Charges de requête et de réponse (formats textuels uniquement : JSON, XML, GraphQL, texte brut)

Détection GraphQL : lorsque des erreurs GraphQL sont détectées, un nouvel attribut supplémentaire est automatiquement inclus sur les événements AjaxRequest :

• operationHasErrors - Indique si l’opération a renvoyé des erreurs

Toutes les données capturées sont automatiquement tronquées à 4 Ko par attribut et prennent en charge les modèles d’obfuscation pour les informations sensibles.

Améliorer l’obfuscation pour prendre en charge le filtre d’événement

Le comportement d'obfuscation peut désormais être configuré pour s'appliquer uniquement à un sous-ensemble de types d'événements, à l'aide de la propriété eventFilter, qui prend en charge un éventail de chaînes de type d'événement par règle d'obfuscation. Lorsqu'elle est fournie, la règle d'obfuscation ne sera appliquée que lorsque le type d'événement correspond à l'un des éléments de l'éventail eventFilter. Pour des raisons de rétrocompatibilité, le fait de ne pas fournir de propriété eventFilter sur les règles de configuration appliquera la règle à toutes les données.

Débogage

Calculer le browser_stack_hash à partir de la trace d’appels tronquée

Calculer le hacher de stack Browser à partir de la trace d’appels tronquée au lieu de la trace d’appels non tronquée. Avant cette modification, les collectes de première occurrence d'événements JSE pouvaient avoir un hacher de stack Browser différent des collectes futures de la même trace d’appels si elle était tronquée. Cela améliorera le regroupement des erreurs des événements JavaScriptError.

Obtenir responseBodySize à partir du corps si content-length est manquant

Résout un problème où les événements AjaxRequest signalaient de manière inexacte un responseSize de 0 ou undefined en raison d'un manque de mécanismes de secours et de vérifications de valeurs fausses trop restrictives. Introduction d'un mécanisme de secours qui calcule les tailles de réponse à partir des charges capturées pour les requests Fetch et XHR lorsque l'en-tête content-length est manquant.

Correction de la gestion de l'intégration des images pour Session Replay

Corrige un problème où Session Replay peut laisser une image cassée dans le DOM en direct. Dans cette version, la version sous-jacente de rrweb évitera de manipuler l’image en direct sur le DOM.

Déclaration de soutien

New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront la fin de leur vie. Les dates de sortie reflètent la date de publication originale de la version de l'agent.

Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce dashboard d'état pour plus d'informations.

Conformément à notre politique de prise en charge des navigateurs, la v1.317.0 de l'agent Browser a été conçue pour et testée sur ces navigateurs et plages de versions : Chrome 139-149, Edge 139-149, Safari 18-26 et Firefox 141-151. Pour les appareils mobiles, la v1.317.0 a été compilée et testée pour Android OS 16 et 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

Caractéristiques

Améliorer l'API SPA pour prendre en charge l'option targetPageLoad

Permettre à l'API SPA de cibler et de travailler sur l'événement BrowserInteraction de type initialPageLoad. Une nouvelle option est ajoutée à .interaction qui lie désormais le handle retourné à l'interaction de chargement initial de la page à tout moment.

Déclaration de soutien

New Relic vous recommande de mettre à niveau l'agent régulièrement pour vous assurer de bénéficier des dernières fonctionnalités et avantages en termes de performances. Les sorties plus anciennes ne seront plus prises en charge lorsqu'elles atteindront la fin de leur vie. Les dates de sortie reflètent la date de publication originale de la version de l'agent.

Les nouveaux agents de navigation sont déployés auprès des clients par petites étapes sur une période donnée. De ce fait, la date à laquelle la sortie devient accessible sur votre compte peut ne pas correspondre à la date de publication d'origine. Veuillez consulter ce dashboard d'état pour plus d'informations.

Conformément à notre politique de prise en charge des navigateurs, la v1.315.0 de l'agent Browser a été conçue pour et testée sur ces navigateurs et plages de versions : Chrome 136-146, Edge 136-146, Safari 18-26 et Firefox 138-148. Pour les appareils mobiles, la v1.315.0 a été compilée et testée pour Android OS 16 et iOS Safari de 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.