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

Monitor Data Wrapper

Each monitor data is wrapped in an envelope data structure with the following format as listed below:

  • dataModelVersion | string
    The version of the wrapper data model. For Example, it might be 2.0, 2.1.

Wrapper and Data Model

Wrapper and actual data model versions are different because wrapper data are not interested in with the actual data itself so their data models can be changed independently from each other.

  • type | string
    Type of the monitoring data. Valid values are:

    Invocation
    Trace
    Span
    Metric
    Log

  • data | string|object
    The monitor data itself. It can be

    JSON formatted object
    Or compressed and encoded string if compression is enabled (compressed property is true)

  • apiKey | string
    API key to be used for sending monitor data.

  • compressed | boolean
    Indicates whether monitor data is first compressed with Gzip and then encoded. To process compressed monitor data, it must be decoded first and then decompressed by Gzip. This field is optional. So if there is no such field, this means that there is no compression.