@sentry/aws-serverless
Advanced tools
@@ -1,1 +0,1 @@ | ||
| {"type":"module","version":"10.15.0","sideEffects":false} | ||
| {"type":"module","version":"10.16.0","sideEffects":false} |
+4
-4
| { | ||
| "name": "@sentry/aws-serverless", | ||
| "version": "10.15.0", | ||
| "version": "10.16.0", | ||
| "description": "Official Sentry SDK for AWS Lambda and AWS Serverless Environments", | ||
@@ -72,4 +72,4 @@ "repository": "git://github.com/getsentry/sentry-javascript.git", | ||
| "@opentelemetry/semantic-conventions": "^1.37.0", | ||
| "@sentry/core": "10.15.0", | ||
| "@sentry/node": "10.15.0", | ||
| "@sentry/core": "10.16.0", | ||
| "@sentry/node": "10.16.0", | ||
| "@types/aws-lambda": "^8.10.62" | ||
@@ -83,3 +83,3 @@ }, | ||
| "build": "run-p build:transpile build:types", | ||
| "build:layer": "rollup -c rollup.lambda-extension.config.mjs && yarn ts-node scripts/buildLambdaLayer.ts", | ||
| "build:layer": "rimraf build/aws && rollup -c rollup.lambda-extension.config.mjs && yarn ts-node scripts/buildLambdaLayer.ts", | ||
| "build:dev": "run-p build:transpile build:types", | ||
@@ -86,0 +86,0 @@ "build:transpile": "rollup -c rollup.npm.config.mjs && yarn build:layer", |
+41
-16
@@ -18,5 +18,24 @@ <p align="center"> | ||
| To use this SDK, call `Sentry.init(options)` at the very beginning of your JavaScript file. | ||
| ### Automatic Setup | ||
| ```javascript | ||
| To use this SDK with an automatic setup, set the following environment variables in your Lambda function configuration: | ||
| ```bash | ||
| NODE_OPTIONS="--import @sentry/aws-serverless/awslambda-auto" | ||
| SENTRY_DSN="__DSN__" | ||
| # 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 | ||
| SENTRY_TRACES_SAMPLE_RATE="1.0" | ||
| ``` | ||
| ### Manual Setup | ||
| Alternatively, to further customize the SDK setup, you can also manually initialize the SDK in your lambda function. The benefit of this installation method is that you can fully customize your Sentry SDK setup in a Sentry.init call. | ||
| Create a new file, for example `instrument.js` to initialize the SDK: | ||
| ```js | ||
| import * as Sentry from '@sentry/aws-serverless'; | ||
@@ -26,5 +45,23 @@ | ||
| dsn: '__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, | ||
| // 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, | ||
| }); | ||
| ``` | ||
| And then load the SDK before your function starts by importing the instrument.js file via a NODE_OPTIONS environment variable: | ||
| ```bash | ||
| NODE_OPTIONS="--import ./instrument.js" | ||
| ``` | ||
| ## Verify | ||
| ```js | ||
| // async (recommended) | ||
@@ -41,16 +78,4 @@ export const handler = async (event, context) => { | ||
| If you also want to trace performance of all the incoming requests and also outgoing AWS service requests, just set the | ||
| `tracesSampleRate` option. | ||
| ## Integrate Sentry using the Sentry Lambda layer | ||
| ```javascript | ||
| import * as Sentry from '@sentry/aws-serverless'; | ||
| Sentry.init({ | ||
| dsn: '__DSN__', | ||
| tracesSampleRate: 1.0, | ||
| }); | ||
| ``` | ||
| #### Integrate Sentry using the Sentry Lambda layer | ||
| Another much simpler way to integrate Sentry to your AWS Lambda function is to add the official layer. | ||
@@ -57,0 +82,0 @@ |
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 5 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 5 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
265335
0.46%88
39.68%+ Added
+ Added
+ Added
+ Added
- Removed
- Removed
- Removed
- Removed
Updated
Updated