fix(otel): Use operation startTimestamp for continuation spans#542
Merged
Conversation
Set the span start time to the operation's original startTimestamp when creating continuation spans in onOperationEnd. Previously the span defaulted to the current wall-clock time, which misrepresented the actual duration of cross-invocation operations. Add a test to verify the continuation span uses the operation's startTimestamp.
nvasiu
approved these changes
Jul 16, 2026
SilanHe
marked this pull request as ready for review
July 16, 2026 21:43
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
3 participants
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.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue Link, if available
Description
Set the span start time to the operation's original startTimestamp when creating continuation spans in onOperationEnd. Previously the span defaulted to the current wall-clock time, which misrepresented the actual duration of cross-invocation operations.
Add a test to verify the continuation span uses the operation's startTimestamp.
Demo/Screenshots
n/a
Checklist
Testing
Unit Tests
Have unit tests been written for these changes? yes
Integration Tests
Have integration tests been written for these changes? no
Examples
Has a new example been added for the change? (if applicable)
no