From 87627e9659db8d4670e0a2236d49fb9072100232 Mon Sep 17 00:00:00 2001 From: Andrei Borza Date: Tue, 11 Nov 2025 17:02:48 +0100 Subject: [PATCH 1/3] chore(aws): Add known issues/remarks for aws + express and infrastructure as code frameworks --- .../guides/aws-lambda/troubleshooting.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx b/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx index 5f0081b39914ef..c5469703082245 100644 --- a/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx @@ -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. + + + +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. + + + + + +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 exempted from bundling. If these libraries are bundled, Sentry cannot instrument them properly, resulting in missing tracing data. + +To fix this, mark these libraries as external in your build configuration. You can ship these libraries via a Lambda layer so your function can still access them at runtime. + + From ce0220bebca33ef1de33deb5c9311b6c14e3fea1 Mon Sep 17 00:00:00 2001 From: Andrei <168741329+andreiborza@users.noreply.github.com> Date: Tue, 11 Nov 2025 17:24:53 +0100 Subject: [PATCH 2/3] Update docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx Co-authored-by: Nicolas Hrubec --- docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx b/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx index c5469703082245..fcfbdd282a6776 100644 --- a/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx @@ -26,7 +26,7 @@ This is expected behavior for the AWS Lambda SDK. See the [related GitHub issue] -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 exempted from bundling. If these libraries are bundled, Sentry cannot instrument them properly, resulting in missing tracing data. +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. To fix this, mark these libraries as external in your build configuration. You can ship these libraries via a Lambda layer so your function can still access them at runtime. From 0b59d79cb3c20ed542f09119a3f44bae49fcebd9 Mon Sep 17 00:00:00 2001 From: Andrei <168741329+andreiborza@users.noreply.github.com> Date: Tue, 11 Nov 2025 17:25:47 +0100 Subject: [PATCH 3/3] Update docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx Co-authored-by: Nicolas Hrubec --- docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx b/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx index fcfbdd282a6776..059e66608dbfcf 100644 --- a/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/troubleshooting.mdx @@ -28,6 +28,6 @@ This is expected behavior for the AWS Lambda SDK. See the [related GitHub issue] 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. -To fix this, mark these libraries as external in your build configuration. You can ship these libraries via a Lambda layer so your function can still access them at runtime. +You can include them via a Lambda layer so that your function can still access them at runtime.