v1.303.0
Caractéristiques
Autoriser l'appel de l'API de consentement sans accès au stockage local
Permet à l'API de consentement de fonctionner sans nécessiter d'accès à localStorage, en conservant un état commun dans l'agent qui contrôle les récoltes. Les applications doivent appeler l'API à chaque chargement de page lorsque l'accès à localStorage est bloqué.
Autoriser les inscriptions imbriquées
Pour faciliter les relations parent-enfant inhérentes avec l'API d'enregistrement prévue, permettre à l'entité enregistrée d'exposer sa propre API .register() pour que les enfants de cette entité puissent s'y enregistrer. Les entités qui s'enregistrent auprès de l'agent conteneur seront liées au conteneur. Une entité qui s'enregistre sous une autre entité enregistrée sera liée à la fois au conteneur et à l'entité parente.
Validation supplémentaire pour préparer l'agent aux enregistrements MFE
Ajout de règles de validation dans l'agent pour empêcher les mauvaises valeurs pour la cible MFE id et name en support des enregistrements MFE/v2.
Ajouter la prise en charge des mesures pour enregistrer l'API
Ajoute la prise en charge de l'API de mesure dans l'objet de réponse d'enregistrement. Ceci soutient la future offre de micro-frontend prévue.
Ajouter la fonctionnalité useConsentModel
Ajoute la propriété et la fonctionnalité d'initialisation use_consent_mode. Ajoute l'appel d'API consent(). Le modèle de consentement, s'il est activé, interdit la collecte d'agents à moins que le consentement ne soit donné via l'appel d'API consent().
Réessayer l'appel de connexion initial
Pour éviter toute perte de données, l'agent va désormais réessayer l'appel « RUM » initial une fois de plus pour les codes d'état pouvant être réessayés.
Ajouter le support des événements personnalisés pour enregistrer l'API
Ajoute des méthodes de capture d'événements personnalisées à l'API d'enregistrement, qui seront utilisées ultérieurement lorsque la prise en charge MFE sera établie.
Réponse SM pour la connexion au navigateur
Ajoute des indicateurs de prise en charge pour les réponses ayant échoué lors de l'initialisation de l'agrégat page_view_event.
Débogage
Obfuscation de l'attribut personnalisé pour le journal ajouté après le JcE
Étend obfuscation pour couvrir l'attribut personnalisé lors de l'événement de journalisation ajouté après la récolte initiale RUM/PageViewEvent.
Mémoriser la propagation du contexte de la promesse pour éviter les blocages de Safari
Mémorise la propagation du contexte des promesses afin d'éviter les blocages potentiels de browser dans Safari en évitant les opérations de contexte répétées.
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 version 1.303.0 de l'agent Browser a été conçue et testée avec les navigateurs et plages de versions suivants : Chrome 131-141, Edge 131-141, Safari 17-26 et Firefox 134-144. Pour les appareils mobiles, la version 1.303.0 a été conçue et testée pour Android OS 16 et iOS Safari 17-26.
v1.302.0
Features
Prepare agent to utilize v2 harvests for MFE registrations
Update the agent to handle harvests for registered targets to use the newly defined v2 endpoint schemas. This will act as the mechanism to handle client-side entity and relationship synthesis as well as ingest MFE specific data. This will be supported for Log, PageAction and JavaScriptError events, but is currently gated behind internal feature flags until a public preview is announced.
Bug fixes
User frustrations logic should be gated
Move user frustrations logic to browser scope only with FF gate in Generic Events instrumentation. This should avoid running extraneous wrapping logic and events related to user frustrations.
Improve accuracy in standalone AjaxRequest event start times
Adjusts a problem in the agent where start times of certain standalone AjaxRequest event payloads were reported relative to the page origin instead of relative to the first event in the payload, causing discrepancies when visualizing in NR1.
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.302.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 134-144. For mobile devices, v1.302.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.301.0
Features
Switch to using NR fork of rrweb
Browser agent will now switch to using New Relic's forked version of rrweb for Session Replay instead of the original repository. This will allow browser team to custom tailor hotfixes for issues.
Bug fixes
Preserve agent attributes for log payloads
Adjust browser log payloads, such that agent-reserved attributes will take precedence over user-provided values if they happen to share the same name.
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.301.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 133-143. For mobile devices, v1.301.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.300.0
Features
Remove usage of the marks and measures feature flag
No longer gates the agent by an internal feature flag. Measures will be enabled for all users by default unless turned off through the application settings.
Reduce hasReplay attribute false positive rate
Only set "hasReplay" attribute once a successful session replay harvest has been observed to help reduce false positives.
Bug fixes
Update typings for interaction API to reflect waitForEnd
Fixes an issue where the typing file defining the .interaction API was not decorated correctly to account for the optional waitForEnd argument as documented.
Address issues with dynamic require and Rollup.js
Fixes an issue that led Rollup.js to spawn the error Error: Could not dynamically require ... when building pages that included the MicroAgent loader.
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.300.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 131-141, Edge 131-141, Safari 17-26, and Firefox 133-143. For mobile devices, v1.300.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.299.0
Features
Add Flutter supportability metric
Introduces a supportability metric to track browser agent usage in Flutter web applications.
Add user frustration signals to UserAction
Provide better insight into potential user frustrations for specific user actions via dead click and error click detections.
Evaluate the accuracy of cross-feature attribution
To support internal improvement benchmarks, add supportability metrics that evaluate the accuracy of attributes that indicate the state of a separate event, such as hasReplay or hasTrace.
Bug fixes
Fix recordReplay API inconsistencies
Fixes an issue where a late-called recordReplay API call would not successfully harvest data.
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.299.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.299.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.298.0
Features
Factor long tasks into soft nav base interaction span
BrowserInteraction under soft navigation ("SPA 2.0") will extend in duration beyond DOM modification time until the point wherein no long tasks have been observed for 5 seconds. JavascriptError and AjaxRequest are not yet associated with such interaction during this extended period beyond the end of the original heuristic.
Bug fixes
Force LCP to report the original page URL
Allow LCP to report its pageUrl distinctly from the harvest URL. An issue was observed where soft navigations occurring before the LCP harvest would report the current page URL instead of the original page URL tied to LCP. This change allows LCP harvest nodes to report the original URL, regardless of the current page URL. The change should apply both to the pageUrl and targetGroupedUrl attributes.
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.298.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.298.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.297.1
Bug fixes
Prevent double import of Session Replay aggregate class
Fixes an issue that was found where the Session Replay aggregate class could be double imported when using the newrelic.recordReplay API method while preloading was enabled.
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.297.1 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 130-140, Edge 130-140, Safari 17-19, and Firefox 132-142. For mobile devices, v1.297.1 was built and tested for Android OS 16 and iOS Safari 17-18.5.
v1.297.0
Features
Prevent early harvests when in retry period
Prevent the agent from harvesting early when being rate limited. If the ingest service returns a 429, the agent will replace its data and try the harvest again later. While that is happening, it will no longer be able to harvest early as new data comes in, until it successfully harvests.
remove newrelic meta attribute
Remove the reporting of the __newrelic meta attribute from outgoing replay payloads. This is being conducted as a measure to help save billable bytes for customers and reduce cost of use for Session Replay functionalities.
Bug fixes
Fix exceptions for null bodies arising from empty harvests
A change has been made to enforce that all cleaned payloads ensure a valid output. Before, an empty string passing through the body cleaning process could throw an error as the mechanism would return the body as null. Now empty strings will pass through untouched, allowing further processing to apply 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.297.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 129-139, Edge 129-139, Safari 17-19, and Firefox 131-141. For mobile devices, v1.297.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.
v1.296.0
Features
Harvest traces early
Update agent to handle session traces the same way other features handle data as of 1.294.0, by allowing harvests at 16kb of size.
Bug fixes
Remove event buffer inspection event
Removes the event buffer inspection event to avoid a memory leak on using console.log with the newrelic window event listener.
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.296.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 129-139, Edge 129-139, Safari 17-19, and Firefox 131-141. For mobile devices, v1.296.0 was built and tested for Android OS 16 and iOS Safari 17-18.1.