-
Notifications
You must be signed in to change notification settings - Fork 56
feat: Retry initial connect call #1605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Supportability Metric Usage Changes:
Supportability Metrics .md File Changes:supportability_metrics.md was changed? New supportability metrics require changes to supportability_metrics.md, as well as a new PR to Angler. Please ensure an Angler PR is created and linked to this PR. |
Asset Size Report
Merging this pull request will result in the following asset size changes:
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1605 +/- ##
==========================================
- Coverage 88.51% 88.36% -0.15%
==========================================
Files 206 206
Lines 7760 7772 +12
Branches 1591 1589 -2
==========================================
- Hits 6869 6868 -1
- Misses 779 791 +12
- Partials 112 113 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
To help prevent data loss, the agent will now retry the original "RUM" call an extra time for retryable status codes.
Overview
Related Issue(s)
Angler PR
https://source.datanerd.us/agents/angler/pull/757
Issue
https://new-relic.atlassian.net/browse/NR-137656?atlOrigin=eyJpIjoiNjI5ODU3OTNkMDA3NDk3ZTg5ODk2YzEwYjgzMjQxNjciLCJwIjoiaiJ9
Testing
New tests have been added to ensure the RUM request is retried and is identical, and subsequent feature will harvest.