feat: maintain a harvestCount for use later with harvestId #922
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.
Add a counter which increments after every harvest. This will be used in a future effort to curate a unique harvest ID for API paging purposes.
Overview
This PR adds a harvestCount int to the runtime object, which increments every time
_send
is completed._send
is used under the hood by all harvest methods to send data. The plan for the future will be to concat this harvestCount with theptid
andsession
values to create a unique harvest identifier on blob-consumer payloads.Related Issue(s)
https://new-relic.atlassian.net/browse/NR-238623
https://new-relic.atlassian.net/browse/NR-238628
Testing
A new, simple jest test has been added to confirm this behavior. WDIO test should be added later when implemented in outgoing harvests