W3C Trace Context purpose of and what kind of problem it came to solve. (by luizhlelis)

Trace-context-w3c Alternatives

Similar projects and alternatives to trace-context-w3c

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better trace-context-w3c alternative or higher similarity.

trace-context-w3c discussion

Log in or Post with

trace-context-w3c reviews and mentions

Posts with mentions or reviews of trace-context-w3c. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-04.
  • Implementing OTel Trace Context Propagation Through Message Brokers with Go
    4 projects | | 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 | | 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?




  • End-to-end tracing with OpenTelemetry
    8 projects | | 31 Aug 2022
  • 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 | | 24 Apr 2022
  • OpenTelemetry and Istio: Everything you need to know
    3 projects | | 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 | | 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 | | 5 Oct 2021
  • Validação de entrada de dados e respostas de erro no ASP.NET
    3 projects | | 18 Aug 2021
  • [c#] Using W3C Trace Context standard in distributed tracing
    9 projects | | 13 Jun 2021
    The main objective is to propagate a message with traceparent id throw two APIs and one worker using W3C trace context standard. The first-api calls the second-api by a http call while the second-api has an asynchronous communication with the worker by a message broker (rabbitmq was chosen for that). Furthermore, zipkin was the trace system chosen (or vendor as the standard call it), being responsible for getting the application traces and building the distributed tracing diagram:
  • A note from our sponsor - SaaSHub | 16 Jun 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic trace-context-w3c repo stats
over 1 year ago

Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.