Instrument RPC calls to amazon SQS#933
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
axw
left a comment
There was a problem hiding this comment.
Looks good, with the caveat that I don't really know SQS. We should be recording trace context (traceparent & tracestate) in message attributes.
Add the trace context header to the message attribute metadata when creating messages.
|
I added the trace context to the message attributes, but when I was inspecting the body for I removed all the instrumentation we do (don't add This is not happening in |
| if tc.hasTraceContext { | ||
| wrapped.Handlers.Build.PushBackNamed(request.NamedHandler{ | ||
| Name: "spy_message_attrs_added", | ||
| Fn: testTracingAttributes(t), |
There was a problem hiding this comment.
Took some inspiration from the ruby client test and added another handler to inspect that the params were correctly modified.
Add support for tracing AWS SQS RPCs when using a wrapped `*session.Session` struct
Add instrumentation for SQS methods for sending/receiving/deleting messages.
Note:
Ignoring message queues is part of the messaging spec, but will be included later. This is being tracked in #934.
closes #883