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
Caractéristiques
Suppression de agentIdentifier
Suppression des références à portée par identifiant d'agent pour simplifier l'architecture de l'agent. Toutes les références sont désormais stockées directement au sein de la référence de l'agent, éliminant ainsi la nécessité de combiner les références de l'agent avec des objets à portée via des clés de recherche.
Attribuer l'URL de la page d'origine à tous les nœuds PageViewTiming
Extension de l'attribution pageUrl à toutes les mesures de temps, en s'appuyant sur les travaux précédents pour le LCP. Les événements PageViewTiming rapportent désormais l'URL de navigation complète d'origine pour tous les types de nœuds, garantissant la cohérence des données pour les SPA même si l'URL change avant la récolte.
améliorer la logique de timing MFE
Amélioration de la capacité de l'agent à identifier le script MFE correct appelant l'API register. Cette amélioration se traduit par des informations de timing plus précises pour les environnements MFE.
Débogage
Imposer des identifiants de chaîne pour les nouveaux enregistrements MFE
Résolution d'un problème où des identifiants de type non-chaîne provoquaient des erreurs lors de la synthèse d'entités MFE. L'agent impose désormais des identifiants de type chaîne et émet un avertissement si un type de données différent est fourni.
Le replaceur circulaire a supprimé les objets réutilisés des collectes
Correction d'un problème où la méthode interne stringify supprimait les pointeurs partagés dans les charges utiles de collecte, entraînant parfois l'absence d'attributs params dans les collectes d'erreurs.
Mettre à jour la RegExp pour éviter un problème de build webpack non minifié
Le caractère $ a été remplacé par son équivalent hexadécimal dans les expressions régulières. Cela empêche Webpack de remplacer incorrectement le caractère lors du processus de build, ce qui provoquait auparavant des échecs de l'agent dans les builds non minifiés.
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.311.0 de l'agent Browser a été conçue pour et testée sur ces navigateurs et plages de versions : Chrome 134-144, Edge 134-144, Safari 18-26 et Firefox 137-147. Pour les appareils mobiles, la version v1.311.0 a été conçue et testée pour Android OS 16 et iOS Safari 18-26.
v1.310.1
Bug fixes
Enhance LCP entry with fallback attribution values
In cases wherein LCP is reported with no attribution entry from web-vitals, the agent will now pass on other default provided attributes such as timeToFirstByte instead of ignoring them.
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.310.1 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.310.1 was built and tested for Android OS 16 and iOS Safari 18-26.
v1.310.0
Features
better MFE timing handling
Improve the detection of script assets reported by the browser which power the MicroFrontEndTiming event's timeToFetch and timeToBeRequested attributes. This change also includes new assetUrl and assetType attributes to better illustrate the assets used to populate the timing data.
Removing old SPA feature & related wrappings entirely
This concludes the complete removal of the old SPA feature that is replaced by Soft Navigations feature. Since agent version 1.307.0, the default "SPA" was already switched over, so no breaking changes from this version are expected.
Capture MFE timings as MicroFrontEndTiming Events
Captures the lifecycle timings of registered entities in preparation for future micro front end product
Bug fixes
Update measure API types
Corrects an issue where the typings associated with the measure API did not accept PerformanceMark as a valid input for start or end values.
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.310.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 134-144, Edge 134-144, Safari 17-26, and Firefox 137-147. For mobile devices, v1.310.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.309.0
Features
Warn when more than one agent is running
Added a console warning when more than one Browser agent is running on the page.
Improve MFE tag setting
Enforce tags to be set for micro frontends by supplying an object of key-value pairs to the tags argument of the register(...) API. This allows for tags to be specified with an explicit value instead of only supporting boolean tags.
Add WebDriver detection attribute to PageView & PageViewTiming
PageView, PageViewTiming and initialPageLoad-category BrowserInteraction events will now report a webdriverDetected property corresponding to the navigator.webdriver set by the browser.
Bug fixes
Micro agent duplicate handlers
Fixes when micro agents are created in a staggered fashion, handlers for each agent is multiplied by the number of agents that follow. For example if there were two agents, the handlers for the first agent was registered twice. This had the effect of duplicating events + contents of harvest payloads.
allow child registrations from blocked parents
Allow blocked parent entities to still instantiate a child MFE when registering
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.309.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.309.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.308.0
Features
add support for mfe tags with the register API
Adds support for adding entity tags through the usage of the register API
add child.id attribute to facilitate MFE cross-linking
Adds a child.id attribute to duplicated data to facilitate future cross-linking in the UI
Add "deregister" API
Adds support for deregistering a registered entity, for use with the upcoming Micro Front End support initiative.
add parent.type attribute to facilitate relationship synthesis
Adds the required parent.type attribute for future relationship synthesis during MFE ingest.
Add default close reason
Add a default close reason of unknown to WebSocket events whose close reason could not be determined.
Bug fixes
enforce non-null values on the numeric fields
Ensure that numeric fields are always reported on WebSocket events by defaulting to 0 instead of undefined
Clean WebSocket URLs
Remove hash fragments and query params from URLs reported on WebSocket events
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.308.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 136-146. For mobile devices, v1.308.0 was built and tested for Android OS 16 and iOS Safari 17-26.
v1.307.0
Caractéristiques
Faire en sorte que la fonctionnalité de navigations douces soit l'option SPA par défaut
La fonctionnalité de navigations douces est désormais la fonctionnalité en cours d'exécution imposée pour les SPA. L'ancienne fonctionnalité SPA, désormais obsolète, ne peut plus être sélectionnée ni utilisée à partir de cette mise à jour.
Ajouter l'option resetSession à l'API setUserId()
Introduit l'option de réinitialisation de la session de l'agent du navigateur lors de la mise à jour d'un identifiant utilisateur via l'API setUserId().
Prise en charge des caractères génériques dans la liste de refus Ajax
Ajoute la prise en charge des caractères génériques, avec le caractère *, à la fonctionnalité de liste de refus AJAX, ce qui permet de remplacer un ou plusieurs caractères dans vos filtres de liste de refus.
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 v1.307.0 de l'agent Browser a été conçue et testée pour ces navigateurs et plages de versions : Chrome 133-143, Edge 133-143, Safari 17-26 et Firefox 136-146. Pour les appareils mobiles, la version v1.307.0 a été conçue et testée pour Android OS 16 et iOS Safari 17-26.
v1.306.0
Features
Control log API through separate RUM flag
Logs captured by the newrelic.log method will now be configurable through settings and controlled separately from wrapped logs. This allows one to be disabled without affecting the other, as in the case that only newrelic.log is desired and not auto instrumented console.
Ensure responseStart is valid before relying on onTTFB
Adds an extra validation step to ensure that responseStart of the nav timing entry is valid before relying on onTTFB to return valid data. The web-vitals library depends on that value to operate correctly, and without a valid TTFB response, the agent will not send the RUM call. This change ensures that fallback measures are taken when responseStart is invalid, to ensure a RUM call is sent more reliably, which helps compatibility with unsupported frameworks such as ElectronJS.
Bug fixes
Remove linebreak syntax from webpack output
Removes the newline character in webpack output to avoid issues with copy-pasting our script as a string inside code.
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.306.0 of the Browser agent was built for and tested against these browsers and version ranges: Chrome 133-143, Edge 133-143, Safari 17-26, and Firefox 135-145. For mobile devices, v1.306.0 was built and tested for Android OS 16 and iOS Safari 17-26.