Trace Propagation and Public API Endpoints in .NET: Part 1 (DisableĀ All)
Blog post from Honeycomb
The W3C trace context specification represents a significant advancement in standardizing telemetry correlation for microservices, but it lacks guidelines on trace propagation limits, leading to potential issues such as unwanted telemetry effects and handling of Personally Identifiable Information (PII). In the .NET environment, trace propagation is managed through DistributedContextPropagator and OpenTelemetry's TextMapPropagator, which can be overridden to control trace data flow. The text illustrates how to disable inbound trace propagation by overriding these classes, emphasizing the importance of careful management of trace headers to avoid processing unwanted or sensitive data. The document highlights the complexity and responsibility involved in debugging distributed systems, suggesting a need for strategic decisions on handling trace data and hinting at more advanced approaches to be discussed in subsequent posts.