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

Metric Support

Thundra Java Metrics

Metric support provides all essential information regarding the performance of your Java Lambda functions, which translate to carefully calculated stats. It lets you examine:

  • Loaded class counts
  • Memory usages
  • Memory usages by pool
  • CPU percentages
  • GC CPU percentages
  • GC counts
  • GC durations
  • Thread count

Detailed information of these statistics can be found here.

Configuring Metrics

For metric support, thundra-agent-lambda-metric module must be added as a dependency:

<dependencies>
    ...

    <dependency> 
        <groupId>io.thundra.agent</groupId> 
        <artifactId>thundra-agent-lambda-metric</artifactId> 
        <version>${thundra.version}</version>
    </dependency> 

    ...
<dependencies>
dependencies { 
    ...

    compile group: 'io.thundra.agent', 
            name: 'thundra-agent-lambda-metric', 
            version: '${thundra.version}' 

    ...
}

Metrics are periodically provided and reported. With the following environment variables, the reporting period can be configured. If one of the (no need to all of them) following periods reach its configured limit, the metric is published:

  • thundra_agent_metric_sample_sampler_timeAware_timeFreq: Configures the time-frequency in milliseconds to to trigger metric reporting. Metrics are provided only once during the specified time period. The default value is 300000 milliseconds (5 minutes).
  • thundra_agent_metric_sample_sampler_countAware_countFreq: Configures the invocation count to trigger metric reporting. Metrics are provided only once at each of the specified invocation count. The default value is 100.

Viewing Metrics

Data provided by Thundra’s Metric support can be viewed by navigating to the Functions Page using the left sidebar menu of the Thundra Console. You will be then presented a list with all the functions sending data to TWC.

Clicking on a function will show you the graphical representation of all the metric support information relating to the function.

Metric Support


Suggested Edits are limited on API Reference Pages

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