-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Comments
After a little digging, I found something similar in the @marshall-lee a couple of questions I had:
Thanks! |
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 "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
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:
|
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)
The text was updated successfully, but these errors were encountered: