You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Is there any way of using tarpc with a TextMapPropagator to propagate opentelemetry headers or to extend the tracing context allowing more properties to pass by (with an HashMap for example)?
This would allow custom opentelemetry implementation to work with tarpc (Datadog for example).
The text was updated successfully, but these errors were encountered:
Thanks for your question! Apologies for the delay in responding.
I don't think this is supported by tarpc today. Can you provide an example of properties that are needed by Datadog? Their docs suggest Datadog supports the W3C trace context standard, so I assume there is some support already, based on what tarpc makes available to Opentelemetry?
Hi !
In my current datadog implementation few custom headers are required: x-datadog-trace-id, x-datadog-parent-id and x-datadog-sampling-priority.
I was looking at something like TextMapPropagator to pass those properties automatically at the bounds of my services. To do so I thing tarpc would need to support some kind of metadata / headers which is not the case right now.
But looking at the doc you linked, it might not be necessary anymore !
Hi,
Is there any way of using tarpc with a TextMapPropagator to propagate opentelemetry headers or to extend the tracing context allowing more properties to pass by (with an HashMap for example)?
This would allow custom opentelemetry implementation to work with tarpc (Datadog for example).
The text was updated successfully, but these errors were encountered: