Thundra

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

FAQ (Frequently Asked Questions)

I can't see my invocations in Thundra. I'm stuck on the on-boarding.

Are you using Amazon VPC? Are your AWS Lambda functions behind the VPC?

If you are using the Amazon VPC service and if your AWS Lambda functions are behind the VPC the Thundra agents are unable to intercept the calls of your functions and basically can't get the data and transfer to Thundra backend.
There might be 2 possible solutions for this listed below:

  1. You can take your AWS Lambda functions outside the Amazon VPC service.
  2. You can still keep your AWS Lambda functions behind the Amazon VPC service and use Thundra in the "Async mode". See here how to set Thundra in the Async mode.
    Please don't forget to keep the thundra-lambda-adapters-cw AWS Lambda function outside of the Amazon VPC.

I'm using Thundra in the Async Mode but I still can't see my invocations in Thundra.

Are you using Amazon VPC service?

If the thundra-lambda-adapters-cw AWS Lambda function is behind your Amazon VPC then Thundra is unable to get the data. You need to take the function outside of the VPC in order to see the data in Thundra.

FAQ (Frequently Asked Questions)


Suggested Edits are limited on API Reference Pages

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