sqsProcessHook no longer available to augment spans per-message

[sam-super]

What version of OpenTelemetry are you using?

"@opentelemetry/auto-instrumentations-node": "0.62.2",
"@opentelemetry/instrumentation-aws-sdk": "0.58.0",

What version of Node are you using?

22.18.0

What did you do?

const sdk = new NodeSDK({
  resource,
  traceExporter: traceExporter,
  spanProcessors: [new node.BatchSpanProcessor(traceExporter, {})],
  instrumentations: [
    getNodeAutoInstrumentations({
      '@opentelemetry/instrumentation-aws-sdk': {
        enabled: true,
        sqsExtractContextPropagationFromPayload: true,
        sqsProcessHook: sqsProcessHook,
      },
    }),
  ],
});

What did you expect to see?

in @opentelemetry/instrumentation-aws-sdk@0.57.0 sqsProcessHook could be defined, but now it's not an option. we were using it to add some extra data to the span based on the sqs message.

What did you see instead?

This has been removed on this PR moving to span links instead of processing spans:
#2345

Additional context

If there is a way to achieve the same using the new version that would be great, but i can't see an option. i tried responseHook but that only works on the response (not on the individual message), so we can't add attributes to the per-message span.

[trentm]

This is (unfortunately) intentional. The sqsProcessHook was removed recently in #2345 (as you noticed). There is some discussion there. The OTel spec for messaging changed (a long time ago) to no longer have "processing" spans and this PR finally catches up to that OTel spec change.

we were using it to add some extra data to the span based on the sqs message.

IIUC there won't even be a processing span anymore. I might be misremembering.

@seemk do you know if my understanding is correct? Or ideas for a workaround?

[pichlermarc]

Yep, as @trentm mentioned, we're in the process of aligning everything to the semantic conventions. The closer we get to stability for these, the less will change in the long run, but there will unfortunately be some breaking changes like this on the way :/

Unfortunately, means that the processing span went away and there are not plans to bring it back as it's not semantic conventions compliant.

I think one of the workarounds is that we re-introduce that hook (possibly under another name), but allowing to add the information to the span link instead (just brainstorming).

@sam-super would it be possible for you to create a custom span in your app instead and adding the data there? 🤔

[sam-super]

Thanks for the context, @pichlermarc. Yes we can create a span in our handling of the message. We extensively use eventbridge with sqs across many services so setting the detail-type as an attribute of the sqs message at the instrumentation layer just made it easier to roll out everywhere.