You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to instrument a NodeJS Lambda using Xray. Throughout the invocation, I create a number of subsegments, and within each, I issue dynamodb queries. The calls to DDB display in the xray trace as a standalone subsegment nested under the root 'Invocation' segment, rather than under my own subsegment.
Is this supported? Do I need to pass in some options to the captureAWSv3Client call or to the client query call directly to indicate what the parent segment is? Since the prescribed best practice is to create the sdk client outside of the lambda handle function so it can be re-used across invocations, should I be calling captureAWSv3Client during each invocation?
Thanks!
The text was updated successfully, but these errors were encountered:
I'm attempting to instrument a NodeJS Lambda using Xray. Throughout the invocation, I create a number of subsegments, and within each, I issue dynamodb queries. The calls to DDB display in the xray trace as a standalone subsegment nested under the root 'Invocation' segment, rather than under my own subsegment.
Is this supported? Do I need to pass in some options to the captureAWSv3Client call or to the client query call directly to indicate what the parent segment is? Since the prescribed best practice is to create the sdk client outside of the lambda handle function so it can be re-used across invocations, should I be calling
captureAWSv3Client
during each invocation?Thanks!
The text was updated successfully, but these errors were encountered: