-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
Meta: Help WantedPackage: serverlessIssues related to the Sentry Serverless SDKIssues related to the Sentry Serverless SDK
Description
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)
Metadata
Metadata
Assignees
Labels
Meta: Help WantedPackage: serverlessIssues related to the Sentry Serverless SDKIssues related to the Sentry Serverless SDK