Skip to content

Add Otel tracing to SQS connector#3221

Merged
ozangunalp merged 1 commit intosmallrye:mainfrom
ozangunalp:sqs_otel_tracing
Nov 20, 2025
Merged

Add Otel tracing to SQS connector#3221
ozangunalp merged 1 commit intosmallrye:mainfrom
ozangunalp:sqs_otel_tracing

Conversation

@ozangunalp
Copy link
Collaborator

Fixes #3188

@ozangunalp
Copy link
Collaborator Author

@majchrzw did you have time to give it a try ?

@majchrzw
Copy link

I will try to do some tests this or next week.

@majchrzw
Copy link

Hi, I've done a few tests and for the most part it looks good but I noticed 2 things:

  1. Not sure if this can be changed or fixed but spans from receiving message and then processing it are not exactly aligned as I would expect them. For example on pic below I belive that "sqs-otel-receiver" span should overlap lower spans that show DB operations as they were invoked inside @incoming method in blocking manner (not sure if blocking or non-blocking matter in that case).
Zrzut ekranu 2025-11-17 o 18 47 44 2. Second issue for me is that errors in processing incoming messages are not visible in tracing. When exception in processing occurs - there are few spans because message is nacked but no info why it happened so it's a bit confusing. Zrzut ekranu 2025-11-17 o 19 01 20 For example here is how http request trace looks when request failed - there's both status and exception showing: Zrzut ekranu 2025-11-17 o 18 42 45

@ozangunalp
Copy link
Collaborator Author

@majchrzw Thanks for giving this a try.

It is cool that most is working correctly.

I think for your expectations on trace spans and exception context, you need to annotate the processing method with @WithSpan so the processing itself has an associated span. The parent propagation with incoming span will be automatic.

@ozangunalp ozangunalp merged commit 8dcbbc9 into smallrye:main Nov 20, 2025
4 checks passed
@ozangunalp ozangunalp modified the milestones: 4.31.0, 4.32.0 Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No traces produces when using reactive-messaging with sqs connector

3 participants