LG-7526: Upgrade NewRelic browser agent to latest#7246
Merged
Conversation
changelog: Internal, Error Monitoring, Upgrade browser error monitoring agent to latest version
aduth
commented
Oct 28, 2022
2 tasks
mitchellhenke
approved these changes
Oct 28, 2022
zachmargolis
approved these changes
Oct 28, 2022
Co-Authored-By: Zach Margolis <zbmargolis@gmail.com>
aduth
added a commit
that referenced
this pull request
Oct 28, 2022
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎫 Ticket
LG-7526
🛠 Summary of changes
Upgrades the New Relic browser instrumentation agent to the latest version.
Why?
unloadevent flagged in a Google Lighthouse auditResources:
🚀 Notes for Deployment
This will require some coordination to assign the affected configuration values in production and int prior to deploy.Edit: As of c31c24a, this is no longer changing the set of configuration keys, so it shouldn't require any revisions to configuration in deployed environments.We should also test this in int prior to going live in production to ensure there's no disruption in data sent to New Relic.