Security News
CISA Brings KEV Data to GitHub
CISA's KEV data is now on GitHub, offering easier access, API integration, commit history tracking, and automated updates for security teams and researchers.
@aws-lambda-powertools/tracer
Advanced tools
The tracer package for the Powertools for AWS Lambda (TypeScript) library
@aws-lambda-powertools/tracer is an npm package designed to simplify the implementation of distributed tracing in AWS Lambda functions. It helps in capturing and propagating trace data, making it easier to monitor and debug serverless applications.
Initialize Tracer
This code initializes the Tracer object, which is the starting point for using the tracing functionalities provided by the package.
const { Tracer } = require('@aws-lambda-powertools/tracer');
const tracer = new Tracer();
Capture Lambda Handler
This code demonstrates how to wrap a Lambda handler with the tracer to automatically capture trace data for the entire function execution.
const { Tracer } = require('@aws-lambda-powertools/tracer');
const tracer = new Tracer();
exports.handler = tracer.captureLambdaHandler(async (event, context) => {
// Your Lambda function code here
return { statusCode: 200, body: 'Hello World' };
});
Capture Method
This code shows how to use the @tracer.captureMethod() decorator to capture trace data for individual methods within a class.
const { Tracer } = require('@aws-lambda-powertools/tracer');
const tracer = new Tracer();
class MyService {
@tracer.captureMethod()
myMethod() {
// Your method code here
}
}
Add Annotation
This code demonstrates how to add custom annotations to the trace, which can be useful for adding additional context to the trace data.
const { Tracer } = require('@aws-lambda-powertools/tracer');
const tracer = new Tracer();
exports.handler = tracer.captureLambdaHandler(async (event, context) => {
tracer.annotate('key', 'value');
// Your Lambda function code here
return { statusCode: 200, body: 'Hello World' };
});
Add Metadata
This code shows how to add custom metadata to the trace, which can be useful for adding structured data to the trace.
const { Tracer } = require('@aws-lambda-powertools/tracer');
const tracer = new Tracer();
exports.handler = tracer.captureLambdaHandler(async (event, context) => {
tracer.addMetadata('key', { foo: 'bar' });
// Your Lambda function code here
return { statusCode: 200, body: 'Hello World' };
});
The aws-xray-sdk package provides similar functionalities for distributed tracing in AWS Lambda functions. It allows you to capture trace data and propagate it across different services. Compared to @aws-lambda-powertools/tracer, aws-xray-sdk is more general-purpose and can be used in a variety of AWS services, not just Lambda.
OpenTelemetry is a popular open-source project that provides a set of APIs, libraries, agents, and instrumentation to enable observability. It supports distributed tracing, metrics, and logging. Compared to @aws-lambda-powertools/tracer, OpenTelemetry is more comprehensive and can be used across different cloud providers and environments.
The datadog-lambda-js package is designed to enable distributed tracing and custom metrics for AWS Lambda functions using Datadog. It provides similar functionalities to @aws-lambda-powertools/tracer but is specifically tailored for integration with Datadog's observability platform.
Powertools for AWS Lambda (TypeScript) is a developer toolkit to implement Serverless best practices and increase developer velocity.
You can use the library in both TypeScript and JavaScript code bases.
The Tracer utility is an opinionated thin wrapper for AWS X-Ray SDK for Node.js, to automatically capture cold starts, trace HTTP(S) clients including fetch
and generate segments and add metadata or annotations to traces.
To get started, install the library by running:
npm i @aws-lambda-powertools/tracer
Add Tracer
to your Lambda handler as decorator:
import type { LambdaInterface } from '@aws-lambda-powertools/commons/types';
import { Tracer } from '@aws-lambda-powertools/tracer';
const tracer = new Tracer({ serviceName: 'serverlessAirline' });
class Lambda implements LambdaInterface {
// Decorate your handler class method
@tracer.captureLambdaHandler()
public async handler(_event: unknown, _context: unknown): Promise<void> {
tracer.getSegment();
}
}
const handlerClass = new Lambda();
export const handler = handlerClass.handler.bind(handlerClass);
or using middy:
import { Tracer } from '@aws-lambda-powertools/tracer';
import { captureLambdaHandler } from '@aws-lambda-powertools/tracer/middleware';
import middy from '@middy/core';
const tracer = new Tracer({ serviceName: 'serverlessAirline' });
const lambdaHandler = async (
_event: unknown,
_context: unknown
): Promise<void> => {
tracer.putAnnotation('successfulBooking', true);
};
// Wrap the handler with middy
export const handler = middy(lambdaHandler)
// Use the middleware by passing the Tracer instance as a parameter
.use(captureLambdaHandler(tracer));
To capture AWS SDK clients, you can use the captureAWSv3Client
method:
import { Tracer } from '@aws-lambda-powertools/tracer';
import { SecretsManagerClient } from '@aws-sdk/client-secrets-manager';
const tracer = new Tracer({ serviceName: 'serverlessAirline' });
// Instrument the AWS SDK client
const client = tracer.captureAWSv3Client(new SecretsManagerClient({}));
export default client;
You can add metadata and annotations to trace:
import { Tracer } from '@aws-lambda-powertools/tracer';
const tracer = new Tracer({ serviceName: 'serverlessAirline' });
export const handler = async (
_event: unknown,
_context: unknown
): Promise<void> => {
const handlerSegment = tracer.getSegment()?.addNewSubsegment('### handler');
handlerSegment && tracer.setSegment(handlerSegment);
tracer.putMetadata('paymentResponse', {
foo: 'bar',
});
tracer.putAnnotation('successfulBooking', true);
handlerSegment?.close();
handlerSegment && tracer.setSegment(handlerSegment?.parent);
};
If you are interested in contributing to this project, please refer to our Contributing Guidelines.
The roadmap of Powertools for AWS Lambda (TypeScript) is driven by customers’ demand.
Help us prioritize upcoming functionalities or utilities
by upvoting existing RFCs and feature requests,
or creating new ones, in this GitHub
repository.
#typescript
- Invite linkKnowing which companies are using this library is important to help prioritize the project internally. If your company is using Powertools for AWS Lambda (TypeScript), you can request to have your name and logo added to the README file by raising a Support Powertools for AWS Lambda (TypeScript) (become a reference) issue.
The following companies, among others, use Powertools:
Share what you did with Powertools for AWS Lambda (TypeScript) 💞💞. Blog post, workshops, presentation, sample apps and others. Check out what the community has already shared about Powertools for AWS Lambda ( TypeScript) here.
This helps us understand who uses Powertools for AWS Lambda (TypeScript) in a non-intrusive way, and helps us gain future investments for other Powertools for AWS Lambda languages. When using Layers, you can add Powertools as a dev dependency to not impact the development process.
This library is licensed under the MIT-0 License. See the LICENSE file.
FAQs
The tracer package for the Powertools for AWS Lambda (TypeScript) library
The npm package @aws-lambda-powertools/tracer receives a total of 93,137 weekly downloads. As such, @aws-lambda-powertools/tracer popularity was classified as popular.
We found that @aws-lambda-powertools/tracer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISA's KEV data is now on GitHub, offering easier access, API integration, commit history tracking, and automated updates for security teams and researchers.
Security News
Opengrep forks Semgrep to preserve open source SAST in response to controversial licensing changes.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.