topic Re: Opentelemtery to trace SQS listeners running as container pods in EKS and exposed via Dynatrace one agent in Open Q&A

Opentelemtery to trace SQS listeners running as container pods in EKS and exposed via Dynatrace one agent

venkateshn2382 — Thu, 30 Nov 2023 08:14:04 GMT

Hi,

I am trying to add open telemetry trace to my golang code. We have around 10 containers deployed in EKS and each of these will read data from SQS, process and post the data to event bridge --> SQS. I would like to add a unique traceid for each sqs message from process1 and trace it where it is in Dynatrace and whether it has completed process10.

Example :

SQS1 - > process1(Kuberenets container) - SQS2 - >process2(Kuberenets container)..etc

I tried to add a default span and trace id within the code of each process but it is not getting recognized as a service in Dynatrace to pulll the OTEL details.

Re: Opentelemtery to trace SQS listeners running as container pods in EKS and exposed via Dynatrace one agent

ChadTurner — Fri, 27 Dec 2024 19:07:15 GMT

@venkateshn2382 were you able to get your trace ID and spans added? If so, would you be able to share with us what you had to do to get it working?

Re: Opentelemtery to trace SQS listeners running as container pods in EKS and exposed via Dynatrace one agent

RohitBisht — Mon, 30 Dec 2024 23:17:34 GMT

Hi @venkateshn2382 ,
I understood you are not using Oneagent for instrumentation and doing manual injection of Otel code.
Are you using this approach?
https://docs.dynatrace.com/docs/shortlink/otel-wt-go

Check if the oneagent feature is enabled, this links traces.

Go to Settings > Preferences > OneAgent features.
Turn on Send W3C Trace Context HTTP headers.

For context propagation check this, probably the headers are getting dropped or blocked.
https://docs.dynatrace.com/docs/shortlink/otel-wt-go#ensure-context-propagation