Implementing OTel Trace Context Propagation Through Message Brokers with Go

• trace-context-w3c

  11 4 0.0 C#

  W3C Trace Context purpose of and what kind of problem it came to solve.

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.

• tracetest

  53 884 9.8 Go

  🔭 Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.

  

Also, please feel free to join our Slack Community, give Tracetest a star on GitHub, or schedule a time to chat 1:1.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• opentelemetry-demo

  18 1,416 9.5 TypeScript

  This repository contains the OpenTelemetry Astronomy Shop, a microservice-based distributed system intended to illustrate the implementation of OpenTelemetry in a near real-world environment.

  

Here is a typical trace from the OpenTelemetry demo project.

• NATS

  106 14,766 9.8 Go

  High-Performance server for NATS.io, the cloud and edge native messaging system.

  

Several message brokers, such as NATS and database queues, are not supported by OpenTelemetry (OTel) SDKs. This article will guide you on how to use context propagation explicitly with these message queues.

Suggest a related project