Skip to content

chore(aws): Add known issues/remarks for aws + express and infrastructure as code frameworks #15472

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Nov 11, 2025
Merged

chore(aws): Add known issues/remarks for aws + express and infrastructure as code frameworks #15472

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
87627e9
chore(aws): Add known issues/remarks for aws + express and infrastruc…
andreiborza Nov 11, 2025
ce0220b
Update docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx
andreiborza Nov 11, 2025
0b59d79
Update docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx
andreiborza Nov 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,19 @@ og_image: /og-images/platforms-javascript-common-troubleshooting.png
Events might be missing right after a Lambda function coldstart. This is a [known issue](https://github.com/getsentry/sentry-javascript/issues/18107) which we are still investigating. Events are sent for subsequent function invocations.

</Expandable>

<Expandable permalink title="Span Names Show Lambda Function Name Instead of Request Path with Express">

When using `@sentry/aws-serverless` with Express, span names are based on the AWS Lambda function name from the Lambda context, rather than the HTTP request path. This differs from `@sentry/node` behavior where span names show the request path.

This is expected behavior for the AWS Lambda SDK. See the [related GitHub issue](https://github.com/getsentry/sentry-javascript/issues/15788) for more details.

</Expandable>

<Expandable permalink title="Missing Tracing Data when using Infrastructure as Code Frameworks (e.g. CDK, Serverless, SST, etc.)">

When using Infrastructure as Code frameworks (e.g. CDK, Serverless, SST, etc.) that bundle everything into a single file, third-party libraries that need to be instrumented by Sentry (such as `express`, `pg`, etc.) must be marked as external and excluded from the bundle. If these libraries are bundled, Sentry cannot instrument them properly, resulting in missing tracing data.

You can include them via a Lambda layer so that your function can still access them at runtime.

</Expandable>
Loading