Back to Explore

aws/aws-xray-sdk-node

GitHub
1 watchersOpen source

Last release:

The official AWS X-Ray SDK for Node.js, provided by AWS, helps you instrument Node.js applications to generate and send AWS X-Ray traces. It includes multiple SDK packages for common frameworks and integrations, and documentation for using the SDK with the X-Ray service. Note that the SDK is scheduled to enter maintenance mode on February 25, 2026, with only critical bug fixes and security updates after that date.

Project status

  • Maintenance status: The repo shows evidence of ongoing development (last upstream push on 2026-04-14), but the most recent tagged updates in the provided history stop at 3.12.0 on 2025-11-20, so there is a publishing gap to compare against.
  • Update cadence: Compared to the listed updates, there was a long interval from 3.10.3 (2025-01-24) to 3.11.0 (2025-10-15), followed by a faster follow-up to 3.12.0 (2025-11-20) (about a 1 month gap). Relative to today (2026-08-12), there is no evidence in the provided list of newer published updates since late 2025.

AI summary generated

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • aws-xray-sdk-node@3.12.0

    Release 3.12.0 bumps aws-xray-sdk-node and all subpackages to 3.12.0. The main code change is in aws-xray-sdk-core Lambda trace extraction, switching from requiring @aws/lambda-invoke-store to reading it from globalThis.awslambda?.InvokeStore.

    Breaking
  • aws-xray-sdk-node@3.11.0

    Release 3.11.0 bumps aws-xray-sdk-core and the related integration packages (Express, Hapi, Fastify, Koa2, Fetch, Restify, MySQL, Postgres, etc.) to the same version. The core change adds support for extracting the X-Ray trace header in AWS Lambda environments using the Lambda Invoke Store instead of relying only on the legacy environment variable.

    Features
  • aws-xray-sdk-node@3.10.3

    Release 3.10.3 bumps the core package and all related adapters/plugins to 3.10.3. The release notes themselves provide no details beyond pointing to the changelog. The actual diff shows a core middleware behavior change around response header handling and changes in the Fastify integration.

  • aws-xray-sdk-node@3.10.2

    Release 3.10.2 bumps aws-xray-sdk-core and related packages to 3.10.2, with targeted fixes in the Fastify and Fetch integrations. The changelog highlights Fastify plugin export changes and a Fetch update to add missing X-Ray headers and expose an enableCapture utility.

    Features
  • aws-xray-sdk-node@3.10.1

    Release 3.10.1 primarily bumps aws-xray-sdk-core to 3.10.1 and, by extension, updates all related integration packages to 3.10.1. The documented functional change is a dependency bump (body-parser, express, and find-my-way) and a claimed addition of the aws-xray-sdk-fetch package. The code diff indicates there are no direct source code changes beyond versioning and dependency updates.

    Features
  • aws-xray-sdk-node@3.10.0

    Release 3.10.0 updates multiple AWS X-Ray SDK subpackages to align with aws-xray-sdk-core 3.10.0 and includes SQL metadata formatting fixes for MySQL and PostgreSQL. It also updates the fetch integration to forward dispatcher-related fetch options to the underlying fetch implementation. The provided release notes themselves do not list specific changes, but the repository changelog does.

    Features
  • aws-xray-sdk-node@3.9.0

    Release 3.9.0 bumps aws-xray-sdk-core to 3.9.0 and updates multiple integrations (express, hapi, mysql, postgres, restify, fastify, koa2) to peer against the new core version. Core behavior changes center on supporting Lambda PassThrough style trace headers, introducing a noOp flag that affects whether X-Amzn-Trace-Id is injected and how headers are validated.

  • aws-xray-sdk-node@3.8.0

    Release 3.8.0 updates aws-xray-sdk-core and all integration packages to 3.8.0, and adds the aws-xray-sdk-fetch integration. The only substantive behavioral change in the provided diff centers on AWS Lambda trace header handling, specifically around facade vs no-op behavior when _X_AMZN_TRACE_ID is missing or invalid.

    Features
  • aws-xray-sdk-node@3.7.0

    Release 3.7.0 is marked as deprecated in the provided release notes, with a pointer to the project CHANGELOG for details. The actual code changes in this release include notable Lambda-specific behavior and tracing header construction updates, plus a TypeScript typing change for the fetch integration.

  • aws-xray-sdk-node@3.6.0

    Release 3.6.0 primarily bumps versions across the monorepo packages to aws-xray-sdk-node@3.6.0 and aws-xray-sdk-core@3.6.0. The changelog also introduces a new instrumentation package, aws-xray-sdk-fetch, which patches both global fetch (Node 18+) and the node-fetch module to create X-Ray subsegments for outgoing HTTP requests.

    Features