No traces produces when using reactive-messaging with sqs connector

[majchrzw]

Hello everyone, I'm using reactive messaging with sqs connector to read messages from my queue. Is there any chance that I can instrument my setup with OTEL to see correlation between traces of sqs messages and traces from my code? I have currently added quarkus-opentelemetry as dependency and set following properties:

quarkus:
  otel:
      instrumentation:
        messaging:
          experimental:
            receive-telemetry:
              enabled: true
        aws-sdk:
          experimental-use-propagator-for-messaging: true
          experimental-record-individual-http-error: true
mp:
  messaging:
    incoming:
      queue:
        tracing-enabled: true

But I don't see any traces in my obervability tools, besides that logs from code executed by queue does not have any trace_id attribute. Have someone by any chance did such setup and maybe can help me to configure it properly?

[ozangunalp]

The sqs connector doesn't have tracing support yet. Would you want to contribute?

[majchrzw]

Thanks for info, I was suspecting it after looking into code. I will think of contribution but I don't have a lot of time and knowledge to do it so it might be difficult

[majchrzw]

Hi @ozangunalp is there any chance that this feature might be added in any near future? if not then maybe u can give me some hints/instruction how to contribute it and someone from my team will try to do it

[ozangunalp]

@majchrzw if you can test it, I can put up something fairly easily.

[majchrzw]

I can test some cases, but I don't send any SQS messages in my code. Let me know what would u like to test, maybe I can do a sample app with sending to also test it.

[ozangunalp]

Some send/receive/process/send scenario should be fine. For everything else I think we need to add more tests to the PR #3221