Skip to content
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

Display AWS SDK context, e.g. DynamoDB table #4159

Closed
mattfysh opened this issue Nov 15, 2021 · 3 comments
Closed

Display AWS SDK context, e.g. DynamoDB table #4159

mattfysh opened this issue Nov 15, 2021 · 3 comments
Labels
Meta: Help Wanted Package: serverless Issues related to the Sentry Serverless SDK

Comments

@mattfysh
Copy link

I'm migrating from AWS Xray to Sentry and one missing feature that is immediately noticeable is the lack of granular AWS context in the trace.

Currently when using the AWS JS SDK to call AWS APIs, it displays as (for example) POST https://dynamodb.ap-southeast-2.amazonaws.com/

It would be great to have the context needed to figure out which table, and which type of operation (get, query, scan, put, update, etc)

@mattfysh
Copy link
Author

After a little digging, I found something similar in the @sentry/serverless package:

https://github.com/getsentry/sentry-javascript/blob/master/packages/serverless/src/awsservices.ts

@marshall-lee a couple of questions I had:

  1. is there a way to get this to work with the @sentry/node package?
  2. could we enrich DynamoDB operations to include the name of the table in the description? Similar to how Lambda and S3 operations current contain function and bucket names respectively.

Thanks!

@github-actions
Copy link
Contributor

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@spaceemotion
Copy link

I have the same issue with a node lambda in AWS. I use DynamoDB as a primary data store, and am currently unable to distinguish which request is what:

  1. Which table is being used
  2. Which index is being used
  3. What action is being performed (set, put, delete, batch get, ...)
  4. what fields are being read (projected attrs.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Meta: Help Wanted Package: serverless Issues related to the Sentry Serverless SDK
Projects
None yet
Development

No branches or pull requests

4 participants