Skip to content
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

Make the end timestamp and mutable span as requirements in onending #4240

Merged

Conversation

dmathieu
Copy link
Member

@dmathieu dmathieu commented Oct 3, 2024

Changes

OnEnding specifies that the ending timestamp should be set when the callback runs, and the span should be mutable.
These are requirements, so it seems like they should be marked as so.

@dmathieu dmathieu marked this pull request as ready for review October 3, 2024 09:15
@dmathieu dmathieu requested review from a team as code owners October 3, 2024 09:15
@pellared pellared added spec:trace Related to the specification/trace directory clarification clarify ambiguity in specification labels Oct 3, 2024
@MrAlias
Copy link
Contributor

MrAlias commented Oct 3, 2024

There is no way to query the end timestamp on the span. Does it matter if it is set or not?

@dmathieu
Copy link
Member Author

dmathieu commented Oct 3, 2024

It does, because if the callback duration will affect the timestamp value if we set it afterwards.

@MrAlias
Copy link
Contributor

MrAlias commented Oct 3, 2024

I see. Should it be clarified that the end time should exclude the time it takes to run the processors? It seems like requiring it being set is more restrictive than it needs to be.

@dmathieu
Copy link
Member Author

dmathieu commented Oct 3, 2024

That makes sense. I've made the change.

@reyang reyang merged commit 630896f into open-telemetry:main Oct 8, 2024
6 checks passed
carlosalberto pushed a commit to carlosalberto/opentelemetry-specification that referenced this pull request Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification clarify ambiguity in specification spec:trace Related to the specification/trace directory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants