I'd consider Thundra a must-have for any serverless application we're building for our clients. The granularity Thundra provides into our distributed microservices is a time and money saver.

The biggest benefit is being able to “see” the issues in our serverless architecture and being able to “pinpoint” them intuitively.

Thundra is one of the great ways to solve observability issues in our serverless application. It's like putting a tracer bullet in our codebase which helps us to pinpoint part of infrastructure which can be improved or is failing. Now, with introduction of the code-analysis feature, Thundra is taking analytics a step further by almost automating parts of code-review process.

Gaining end-to-end visibility and management for our serverless stack and increasing developer productivity and high application performance while proactively managing using metrics and benchmarks was a big win for us.

With easy set-up in minutes, Thundra lets us quickly dig deep into our serverless data pipeline. We identify and solve issues even before they happen, thanks to the insights provided by Thundra.

It brought us much more insights into errors happening and tracking them down which we were missing for some years now. The tagging feature is awesome as it brings us the ability to track issues based specifically per customer.

Thundra allows us to keep a great overview of our Serverless AWS environment as we can easily monitor lambda performance, cold starts, errors and costs. The detailed tracing functionality and the ability to tag invocations with user ids and error codes have been proven invaluable