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


Thundra Integrator CloudFormation setup fails with message, "This account is currently blocked and not recognized as a valid account".

Check your AWS EC2 resource limits :

  1. Open the Amazon EC2 console at
  2. From the navigation bar, select the region where you run the Thundra-Splunk Integrator CloudFormation setup.
  3. From the navigation pane, choose Limits and make sure that you have sufficient account limits for the specific instance type that you want to run the Thundra-Splunk Integrator.

Logs are transmitted to the the AWS Thundra-Splunk Integrator but not transmitted to my Splunk Instance

If the Thundra-Splunk Integrator receives the logs but your Splunk instance still shows no Lambda data, check that you have opened the appropriate receiver port in your Splunk instance.

Follow the Splunk instructions for opening up port 9997:

Below is a screenshot of where these settings are applied:

Enabling a receiver port in Splunk Application.

Enabling a receiver port in Splunk Application.


Suggested Edits are limited on API Reference Pages

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