Comments (5)
Thanks @ppatierno for filing this issue, and apologies on the delay in our response.
We discussed this in the DT working group meeting today. Yes, it makes sense to specify how to handle trace context propagation for messaging systems in general (where we think there will be good overlap across many of the common/popular systems). That said, the working group doesn't have the bandwidth and messaging expertise at this point to take this up to drive it further. If you would like to be involved in this effort, please let us know.
from trace-context.
@kalyanaj thanks for answering!
May I ask what would be the process (i.e. expectations, steps, tooling, ...) to have something out, in order for me to evaluate the workload and the bandwidth as well? My expectation would be writing something similar to what we have for MQTT and AMQP but for the Kafka protocol. Unless you have more in mind. Thanks!
from trace-context.
Hi @ppatierno, sorry about the delay in getting back. We have a protocol registry: please see https://w3c.github.io/trace-context-protocols-registry/#registration-entry-requirements-and-update-process for the process to include trace context specification for a new protocol. We recommend that if you produce the trace context specification for the Kafka protocol, you can ask us to link to it from this protocol registry.
from trace-context.
Hi @kalyanaj no worries ;-) ... thanks for replying.
I have a couple of question related to what is written at that link.
Each entry should include a link that references a public available specification (PAS) that defines the trace context [TRACE-CONTEXT] serialization and deserialization for that protocol.
What's the way to push such a specification as there are for AMQP and MQTT hosted on the https://w3c.github.io/ website? Is there a specific repo to open and push a PR? Or it can be hosted somewhere else?
I noticed that the CloudEvents specification has a link out of W3C but right now the link is broken.
FYI, it seems that the new link is this one but I am not part of the CloudEvents community to confirm that.
Each entry must include contact information of the requestor.
I see that right now there is W3C and CloudEvents. Has it to be a company? A community? A foundation?
What about the editors? What should be the relationship between editors and requestor?
from trace-context.
Thanks @ppatierno. Yes, the recommendation is to host it externally and link to it from here. BTW, I have created a PR to fix the broken link for the cloudevents specification (w3c/trace-context-protocols-registry#13).
I see that right now there is W3C and CloudEvents. Has it to be a company? A community? A foundation?
What about the editors? What should be the relationship between editors and requestor?
My understanding is that it can be anything (a company / community / foundation etc.) - there are no restrictions/constraints. Basically, in this case this process is happening external to W3C and you are linking to that specification from this protocol registry. Adding @plehegar in case he wants to clarify/add anything.
from trace-context.
Related Issues (20)
- Adopt either span-id or parent-id for section headings HOT 4
- When headers should be propagated in browsers should be made more clear HOT 2
- Change the defining document for HTTP from RFC7230 to RFC9110 HOT 2
- Update tests to test Trace Context level 2 by default
- Incorporate Level 2 changes (random trace id flag) into traceresponse header in Level 3
- Add more normative text for flags processing in traceresponse
- Level 3 spec: Update privacy section to include information about traceresponse headers.
- Random part of trace ID should be uniformly distributed HOT 3
- Autopublishing level2/Level3 specs need to work with multiple markdown files HOT 2
- Document handling of tracestate duplicate keys HOT 6
- Does this specification define a way to handle retries? HOT 4
- Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service HOT 6
- Proposal: Allow common base64 encoding in tracestate values HOT 5
- Should tracing headers be included in 304 Not Modified responses? HOT 14
- Revisit header name -- Server-Timing vs. traceresponse HOT 9
- Server-timing names HOT 6
- Remove all markdown includes
- Can Traceresponse enable parent-child relationship between browser and server spans?
- Trace Context Extensibility HOT 7
- request for clarification re size of parent-id HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from trace-context.