HTTP: Semantic conventions do not seem to allow for intentional cancellations of requests #3495
Description
Area(s)
No response
What's missing?
From https://cloud-native.slack.com/archives/C041APFBYQP/p1771941501331409
I've got a question regarding client spans for http requests that were intentionally cancelled by the client. Which attributes would you expect to be set on these? I'm especially thinking about how to convey that this request did neither fail, not complete.
...
do I read that there is an agreement that, if instrumentations COULD know that a cancellation is intentional, the CLIENT span SHOULD have status code UNSET?
absolutely and it's already part of the conventions. Can we emphasize it better? BTW, you're amazing at finding things we didn't explain clear enough (among other things) 🙂
Describe the solution you'd like
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.