NPM Package - ESM
Learn how to set up Sentry manually for Lambda functions running in EcmaScript Modules (ESM) using Sentry's AWS Serverless SDK NPM package
In this guide you will learn how to set up the @sentry/aws-serverless SDK for AWS Lambda functions running in EcmaScript Modules (ESM) mode. We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function. If you need more control over the SDK setup, you can also initialize the SDK in in code.
At this time, this guide shows the only way to use Sentry with ESM lambda functions. You cannot use the Sentry AWS Lambda Layer with ESM. We're working on an ESM lambda layer to provide a simpler setup but need to solve several OpenTelemetry-related limitations first.
Before you begin, make sure you have the following:
- You have a lambda function that is running in EcmaScript Modules (ESM) mode, using
importsyntax. - You're able to deploy dependencies (i.e.
node_modules) alongside your function code to AWS Lambda.
In addition to capturing errors, you can monitor interactions between multiple services or applications by enabling tracing. You can also collect and analyze performance profiles from real users with profiling.
Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.
Install the @sentry/aws-serverless SDK using a package manager of your choice:
npm install @sentry/aws-serverless
npm install @sentry/aws-serverless
yarn add @sentry/aws-serverless
pnpm add @sentry/aws-serverless
npm install @sentry/aws-serverless @sentry/profiling-node
npm install @sentry/aws-serverless @sentry/profiling-node
yarn add @sentry/aws-serverless @sentry/profiling-node
pnpm add @sentry/aws-serverless @sentry/profiling-node
Add the Sentry.wrapHandler wrapper around your function handler to automatically catch errors and performance data:
index.mjsimport * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
// Your handler code
});
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
// Your handler code
});
To initialize and configure the SDK, you need to set the following environment variables in your AWS Lambda function configuration:
NODE_OPTIONS="--import @sentry/aws-serverless/awslambda-auto"
SENTRY_DSN="___PUBLIC_DSN___"
# ___PRODUCT_OPTION_START___ performance
SENTRY_TRACES_SAMPLE_RATE="1.0"
# ___PRODUCT_OPTION_END___ performance
NODE_OPTIONS="--import @sentry/aws-serverless/awslambda-auto"
SENTRY_DSN="___PUBLIC_DSN___"
# ___PRODUCT_OPTION_START___ performance
SENTRY_TRACES_SAMPLE_RATE="1.0"
# ___PRODUCT_OPTION_END___ performance
To set environment variables, navigate to your Lambda function, select Configuration, then Environment variables:
That's it - make sure to re-deploy your function and you're all set!
To further customize the SDK setup, you can also manually initialize the SDK in your lambda function. Due to ESM limitations, you need to initialize the SDK in a separate file and load it before your function starts. The benefit of this installation method is that you can fully customize your Sentry SDK setup in a Sentry.init call.
Follow steps 1 and 2 above to install the SDK NPM package in your project.
Create a new file, for example instrument.mjs to initialize the SDK:
instrument.mjsimport * as Sentry from "@sentry/aws-serverless";
// ___PRODUCT_OPTION_START___ profiling
import { nodeProfilingIntegration } from "@sentry/profiling-node";
// ___PRODUCT_OPTION_END___ profiling
Sentry.init({
dsn: "___PUBLIC_DSN___",
// Adds request headers and IP for users, for more info visit:
// https://docs.sentry.io/platforms/javascript/guides/aws-lambda/configuration/options/#sendDefaultPii
sendDefaultPii: true,
// ___PRODUCT_OPTION_START___ profiling
integrations: [nodeProfilingIntegration()],
// ___PRODUCT_OPTION_END___ profiling
// ___PRODUCT_OPTION_START___ performance
// Add Tracing by setting tracesSampleRate and adding integration
// Set tracesSampleRate to 1.0 to capture 100% of transactions
// We recommend adjusting this value in production
// Learn more at
// https://docs.sentry.io/platforms/javascript/configuration/options/#traces-sample-rate
tracesSampleRate: 1.0,
// ___PRODUCT_OPTION_END___ performance
// ___PRODUCT_OPTION_START___ profiling
// Set sampling rate for profiling - this is relative to tracesSampleRate
profilesSampleRate: 1.0,
// ___PRODUCT_OPTION_END___ profiling
});
import * as Sentry from "@sentry/aws-serverless";
// ___PRODUCT_OPTION_START___ profiling
import { nodeProfilingIntegration } from "@sentry/profiling-node";
// ___PRODUCT_OPTION_END___ profiling
Sentry.init({
dsn: "___PUBLIC_DSN___",
// Adds request headers and IP for users, for more info visit:
// https://docs.sentry.io/platforms/javascript/guides/aws-lambda/configuration/options/#sendDefaultPii
sendDefaultPii: true,
// ___PRODUCT_OPTION_START___ profiling
integrations: [nodeProfilingIntegration()],
// ___PRODUCT_OPTION_END___ profiling
// ___PRODUCT_OPTION_START___ performance
// Add Tracing by setting tracesSampleRate and adding integration
// Set tracesSampleRate to 1.0 to capture 100% of transactions
// We recommend adjusting this value in production
// Learn more at
// https://docs.sentry.io/platforms/javascript/configuration/options/#traces-sample-rate
tracesSampleRate: 1.0,
// ___PRODUCT_OPTION_END___ performance
// ___PRODUCT_OPTION_START___ profiling
// Set sampling rate for profiling - this is relative to tracesSampleRate
profilesSampleRate: 1.0,
// ___PRODUCT_OPTION_END___ profiling
});
Add the Sentry.wrapHandler wrapper around your function handler to automatically catch errors and performance data:
index.mjsimport * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
// Your handler code
});
import * as Sentry from "@sentry/aws-serverless";
export const handler = Sentry.wrapHandler(async (event, context) => {
// Your handler code
});
To load the SDK before your function starts, you need to preload the instrument.mjs by setting the NODE_OPTIONS environment variable:
NODE_OPTIONS="--import ./instrument.mjs"
NODE_OPTIONS="--import ./instrument.mjs"
To set environment variables, navigate to your Lambda function, select Configuration, then Environment variables:
That's it - make sure to re-deploy your function and you're all set!
The v7 @sentry/serverless SDK does not work correctly with ESM-based Lambda functions. Please upgrade to the latest SDK and follow the instructions above.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").