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

Automated vs Manual Instrumentation

Thundra provides the ability to check the specifics of how your Lambda function performs. This is represented in the spans that are born from Thundra’s trace support which is available for the separate agents. Hence allowing you to visualize which functions call other functions and when they are called, including parameters such as arguments, errors and return values. Different agents require different ways of instrumentation and instructions relating to each agent can be found under the instrumentation of your function section of each agent.

Both manual and automated instrumentation allow you to monitor your Lambda functions in the same manner, but where you would use them is different. Automated instrumentation has the obvious advantage of being easier to configure, but there are applications where you would find yourself preferring manual instrumentation. Hence this post aims to highlight the various applications where you would either use automated instrumentation over manual instrumentation and vice-versa.

Automated vs Manual Instrumentation

Suggested Edits are limited on API Reference Pages

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