Thundra: Serverless Observability for AWS Lambda

The black box nature of AWS Lambda and other serverless environments means that identifying and fixing performance issues is difficult and time-consuming. Built for straightforward debugging, monitoring, and observability, Thundra provides deep insight into your entire serverless environment. Thundra collects and correlates all your metrics, logs, and traces, allowing you to quickly identify problematic invocations and also analyzes external services associated with that function. With Thundra’s zero overhead and automated instrumentation capabilities, your developers are free to write code without worrying about bulking up their Lambdas or wasting time on chasing black box problems.

Get Started    Discussions

How to Warmup

This part is not mandatory but if you want to warmup your lambda functions follow along.

With Thundra's Warmup Lambda you can keep your function warm to avoid cold starts as much as possible.

Take the following steps to setup warmup support (user-end):

  • Thundra provides a Lambda function called thundra-lambda-warmup on the user end to trigger Lambda functions with warmup messages periodically. This function must be deployed once.
  • Specify the Lambda functions to be warmed-up.

The following ways are supported to setup thundra-lambda-warmup on user end:

Manual Setup

If the user end is not an automated deployment environment, setup thundra-lambda-warmup manually on user end by CloudFormation template.

Serverless Framework

Deploys thundra-lambda-warmup by using Serverless framework. If a Serverless framework is already used for deploying your Lambda functions, this is the recommended option with the least number of manual actions.

NOTE: Currently Java, Node.js, Python and .Net agents have warmup support. Others are going to support soon.

How to Warmup

This part is not mandatory but if you want to warmup your lambda functions follow along.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.