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

API Keys are used for authenticating, identifying requests and applying rate limiting to the requests.

Each user has an account based "request per minute" capacity, which limits the number of monitor data that can be sent in a minute, and this capacity is shared by API Keys.

Click CREATE API KEY button to set request limit per minute and determine an alias for you key. This alias will help you to remember that key easily.

An API Key can be “disabled” by setting it’s RPM to 0, or can be deleted optionally.

So each API key has its own "request limit per minute" capacity and sum of these capacities cannot be exceed account based capacity. The default RPM capacity is currently set to 1000.

You can divide that capacity for each API Key as much as you want.

Also you can observe api key usages from Usages tab: