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

Trace Support

Thundra's .NET agent allows you to use trace data to evaluate the running of your function in terms of duration and response and request. At the moment, instrumentation of your .NET function, as in other agents is not yet supported, and hence you cannot see spans or integration of external services at the moment. Nevertheless, basic trace support is available for your .NET functions.

Configuring Trace

Trace support can be configured in three various ways. This involves programmatic configuration, configuration via environment variables, and finally, using configuration files. All three ways allow you to configure your .NET function to enable and disable trace support. By default, trace support is enabled, and upon invoking your lambda expression you can always procure its trace data on the Thundra console.

Dependency when using Programmatic Configuration

If you opt to disable your trace data using programmatic configuration, please ensure you state using Thundra.Agent.Lambda.Config;

 protected override ThundraConfig GetConfig()
   var config  =  new ThundraConfig();
   config.ApiKey = "demo_thundra_Api_Key";
   config.DisableTrace = "true";
   return config;
    "thundra": {
        "properties": {
            "thundra_apiKey" : "demo_thundra_Api_key",
          	"thundra_agent_lambda_trace_disable": "true"

Viewing Trace

Trace data of your .NET Lambda invocations can be seen when you enter the Invocations detail page displaying information about specific information. The trace data is present in the Trace Chart section of the page and upon clicking on the trace you can view the trace 'Summary', 'Logs', and 'Tags'.

Configuring Trace Response/Request

If you would like to disable the 'Response' or 'Request' data that can be viewed when you open your trace data then you can also go about one of the three ways as described when configuring the main trace data above. here you shall use the following environment variables and parameters:

Environment Variables

  • thundra_agent_lambda_trace_response_skip - Set to 'true' to disable response data
  • thundra_agent_lambda_trace_request_skip - Set to 'true' to disable request data

Programmatic Parameters

  • SkipResponse - Set to 'true' to disable response data
  • SkipRequest - Set to 'true' to disable request data

Trace Support

Suggested Edits are limited on API Reference Pages

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