-
Notifications
You must be signed in to change notification settings - Fork 74
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
Provide vendor/open source product name register for tracestate #58
Comments
As a first step we can simply start a document that acts as an informal registry. Good enough? |
Yes, agree. |
@wu-sheng I pushed back on the PR as I think it goes to far. Can we start with a list of reserved names e.g. nr for new relic, dt for dynatrace etc. I don't want specify the format of the tags, because I also don't think this is necessary. I think having two tracers of the same time is different problems, so I would create a separate issue for this. |
I am OK with that, if others agree. I start this because SkyWalking is actually facing this, and provided advanced namespace feature, which will be released in 5.0.0 beta. |
Any update on this? I think there was some good progress on #88 which was later discarded. As people start implementing this, I think it's important to have. |
It would be good to have this. We're already actively using tracestate with our own key ("dt" for now). How would we wanna track this registry? Separate github repo? Document in this repo? |
As we now have the registry, I assume we can close this? |
Sorry, where do we have the registry? |
We have the registry available now. |
once again, where is the registry? |
@yurishkuro it's here https://github.com/w3c/trace-state-ids-registry but we clearly have to add that to make this more visible. Reopening to track this. |
Even there it's just a placeholder, nobody actually registered their IDs? |
The registry is in effect and will be filled now by vendors. |
Based on our workshop, see #57 . Every product need a name in header, which should be unique in global, in order to make sure the context is safe for each vendor or product.
I proposal to maintain a vendors or products name register list, to make sure no conflict about name.
The text was updated successfully, but these errors were encountered: