b3-propagation

Repository that describes and sometimes implements B3 propagation (by openzipkin)

B3-propagation Alternatives

Similar projects and alternatives to b3-propagation

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

b3-propagation reviews and mentions

Posts with mentions or reviews of b3-propagation. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-28.
  • 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/

  • 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).
  • Spring Cloud Sleuth in action
    6 projects | dev.to | 4 Mar 2021
    The default format for context propagation is B3 so we use headers X-B3-TraceId and X-B3-SpanId
  • A note from our sponsor - WorkOS
    workos.com | 29 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →

Stats

Basic b3-propagation repo stats
3
516
2.7
2 months ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com