fix: Fixed api.getTraceMetadata
to handle when there is an active transaction but not active segment
#2944
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.
Description
A regression existed from the refactor of 12.11.0. A PR(#2943) was opened around a gap in test coveraege around this
getTraceMetadata
method. A customer had an active transaction but not segment. We assumed this could never happen, however this does happen at times due to context propagation breaking. This PR addresses this issue by handling of addingtraceId
andspanId
separately. The customer experiencing this will still have invalid trace metadata(lacking a spanId) but that's a different issue.