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 am fiddling around to get Error Tracking working using aws-cdk-v2, datadog-cdk-construct-v2 and NodejsFunction.
It would be nice to have this integrated into this construct library.
I do not know if the following setup is supported at all as there is a related issue in the dd-trace-js repository.
Expected behaviour is: When using a NodeJS Lambda function, I want error tracking in Datadog to show the source code in the stack trace (even for a handler which was bundled and minified via esbuild).
The reason why I believe this is important: The current sourceCodeIntegration does not seem to work out-of-the-box. APM error tracking cannot make sense of the NodeJS Lambda stack traces.
Actual Behavior
There is no matching source code file or source map for the bundled, minified Lambda handler /var/task/index.js.
Steps to Reproduce the Problem
Use the datadog construct with .addGitCommitMetadata
Use a NodejsLambda with the following bundling options:
Expected Behavior
I am fiddling around to get Error Tracking working using aws-cdk-v2, datadog-cdk-construct-v2 and NodejsFunction.
It would be nice to have this integrated into this construct library.
I do not know if the following setup is supported at all as there is a related issue in the dd-trace-js repository.
Expected behaviour is: When using a NodeJS Lambda function, I want error tracking in Datadog to show the source code in the stack trace (even for a handler which was bundled and minified via esbuild).
The reason why I believe this is important: The current
sourceCodeIntegration
does not seem to work out-of-the-box. APM error tracking cannot make sense of the NodeJS Lambda stack traces.Actual Behavior
There is no matching source code file or source map for the bundled, minified Lambda handler
/var/task/index.js
.Steps to Reproduce the Problem
.addGitCommitMetadata
Specifications
The text was updated successfully, but these errors were encountered: