Provide vendor/open source product name register for tracestate about trace-context HOT 13 CLOSED

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.

@AloisReitbauer @SergeyKanzhelev?

from trace-context.

As a first step we can simply start a document that acts as an informal registry. Good enough?

from trace-context.

Yes, agree.

from trace-context.

@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.

from trace-context.

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.

from trace-context.

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?

from trace-context.

As we now have the registry, I assume we can close this?

from trace-context.

Sorry, where do we have the registry?

from trace-context.

We have the registry available now.

from trace-context.

once again, where is the registry?

from trace-context.

@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.

from trace-context.

Even there it's just a placeholder, nobody actually registered their IDs?

from trace-context.

The registry is in effect and will be filled now by vendors.
Anyone interested in registering their ID please join

from trace-context.