-
Notifications
You must be signed in to change notification settings - Fork 897
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
Make the end timestamp and mutable span as requirements in onending #4240
Conversation
There is no way to query the end timestamp on the span. Does it matter if it is set or not? |
It does, because if the callback duration will affect the timestamp value if we set it afterwards. |
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. |
That makes sense. I've made the change. |
Co-authored-by: Cijo Thomas <[email protected]>
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.