Trace-context-w3c Alternatives

trace-context-w3c reviews and mentions

• Devfest Nantes 2024, la frayeur s'invite à la cité des congrès 👻
  2 projects | dev.to | 19 Nov 2024
• How we made applications observable by default with OpenTelemetry
  4 projects | dev.to | 28 Aug 2024

  This is where things get complicated. Implementing such a system is a lot of work, and you should rely on upcoming standards like the W3C recommendation on trace contexts. You should rely on a standard because they solve two major pain points with observability: (1) they have popular implementations like OpenTelemetry (OTel) – which happens to be the second most active CNCF project to this day – and (2) they are widely adopted by major observability backends (e.g., Datadog).

• Implementing OTel Trace Context Propagation Through Message Brokers with Go
  4 projects | dev.to | 4 Apr 2024

  The answer is Context Propagation. The HTTP example is a classic and W3C even covers it. The propagation is adding the important fields from the context into the HTTP headers and having the other application extract those values and inject them into its trace context. This concept applies to any other way of communication. Here, we will focus on message brokers and how you can achieve context propagation for those.

• OpenTelemetry in 2023
  36 projects | news.ycombinator.com | 28 Aug 2023

  I've been playing with OTEL for a while, with a few backends like Jaeger and Zipkin, and am trying to figure out a way to perform end to end timing measurements across a graph of services triggered by any of several events.

  Consider this scenario: There is a collection of services that talk to one another, and not all use HTTP. Say agent A0 makes a connection to agent A1, this is observed by service S0 which triggers service S1 to make calls to S2 and S3, which propagate elsewhere and return answers.

  If we limit the scope of this problem to services explicitly making HTTP calls to other services, we can easily use the Propagators API [1] and use X-B3 headers [2] to propagate the trace context (trace ID, span ID, parent span ID) across this graph, from the origin through to the destination and back. This allows me to query the metrics collector (Jaeger or Zipkin) using this trace ID, look at the timestamps originating at the various services and do a T_end - T_start to determine the overall time taken by one call for a round trip across all the related services.

  However, this breaks when a subset of these functions cannot propagate the B3 trace IDs for various reasons (e.g., a service is watching a specific state and acts when the state changes). I've been looking into OTEL and other related non-OTEL ways to capture metrics, but it appears there's not much research into this area though it does not seem like a unique or new problem.

  Has anyone here looked at this scenario, and have you had any luck with OTEL or other mechanisms to get results?

  [1] https://opentelemetry.io/docs/specs/otel/context/api-propaga...

  [2] https://github.com/openzipkin/b3-propagation

  [3] https://www.w3.org/TR/trace-context/

• End-to-end tracing with OpenTelemetry
  8 projects | dev.to | 31 Aug 2022

  -- https://www.w3.org/TR/trace-context/

• Event Driven Architecture — 5 Pitfalls to Avoid
  1 project | /r/softwarearchitecture | 15 Aug 2022

  For context propagation, why not just reuse the existing trace context that most frameworks and toolkits generate for http requests? I've had to apply some elbow grease to get it play nice but once it does you're able to use tools like Jeager, etc as part of your asynchronous flow as well.

• W3C Recommendation – Trace Context
  1 project | news.ycombinator.com | 24 Apr 2022
• OpenTelemetry and Istio: Everything you need to know
  3 projects | dev.to | 3 Feb 2022

  (Note that OpenTelemetry uses, by default, the W3C context propagation specification, while Istio uses the B3 context propagation specification – this can be modified).

• What is Context Propagation in Distributed Tracing?
  5 projects | dev.to | 2 Feb 2022

  World Wide Web Consortium (W3C) has recommendations on the format of trace contexts. The aim is to develop a standardized format of passing trace context over standard protocols like HTTP. It saves a lot of time in distributed tracing implementation and ensures interoperability between various tracing tools.

• My Logging Best Practices
  3 projects | news.ycombinator.com | 5 Oct 2021
• A note from our sponsor - SaaSHub
  www.saashub.com | 17 Mar 2025

  SaaSHub helps you find the best software and product alternatives Learn more →