-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add instrumentation for AWS SQS and SNS #978
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
💔 Build Failed
Expand to view the summary
Build stats
Trends 🧪Steps errorsExpand to view the steps failures
|
estolfo
changed the title
Add instrumentation for AWS SQS
Add instrumentation for AWS SQS and SNS
Mar 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added support for SNS and SQS in the same PR because they both depend on some additions to the span context.
SQS
Note that there is no instrumentation for polling, as you can poll a SQS queue by doing one of the following two things:
wait_time_seconds
when callingclient#receive_message
. So the action is stillRECEIVE
, though with a longer timeout. I didn't see that it was necessary to inspect the method params for await_time_seconds
value and identify the action asPOLL
instead ofRECEIVE
in the case that it was set.QueuePoller.poll
just callsreceive_message
on a client in a loop. So I didn't think it necessary to instrument this class, as the user will see the individualRECEIVE
actions instrumented anyway.This PR also adds a class
Message
that allowsspan.context.message
fields to be added.And lastly, the SQS instrumentation may look repetitive but each method differs slightly. For example, we must iterate over the
params[:entries]
in order to add trace context info to messages sent viasend_message_batch
, as opposed to adding the info directly to theparams
. I thought it would make the code more confusing if I tried to centralize the instrumentation into one method that handled slight differences.See the spec here
Closes #946
SNS
Closes #945