fix(js): process spans in isolation to improve accuracy of telemetry #3113
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.
Span processing in the google-cloud plugin is currently done in batches, which are chosen by the OTel libraries. We erroneously rely on each batch being a complete representation of a trace, and to contain only spans from a single trace. Since these assumptions are incorrect there are currently subtle bugs where span metrics and logs are being mis-attributed, or dropped. This change removes the need for the above assumptions, by processing each span entirely independently.
We also remove some unused logs/metrics for simplicity, and improve the test coverage around "path" telemetry.
Checklist (if applicable):