Server-timing names
Open
Nobody has claimed this yet.
trace-context-level-3
- Dominant language
- Python
- Stars
- 510
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
Following up on https://github.com/w3c/trace-context/pull/560
The possible alternative for naming would be:
instead of:
server-timing: trace;tid=0af7651916cd43dd8448eb211c80319c,cid=b7ad6b7169203331
use
server-timing: span;id=b7ad6b7169203331,tid=0af7651916cd43dd8448eb211c80319c
Benefits:
- It is already clear that the information about "server" - meaning we should not even introduce the term "child".
- Opens a door to add span name and duration to the same list and make it into a metric
- Does not require introducing naming distributed-trace or similar to clarify what trace means
- Makes it more natural to understand which one is "ID" without understanding what the difference between "c" and "t"
- Shortens 2 characters
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked pull request #560 and the naming alternatives shown in this issue. Compare the proposed Server-Timing terms with the surrounding Trace Context specification and discussion. Done means maintainers agree on the terminology and the relevant specification examples consistently reflect that choice.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100