Setting up alerts for your serverless transactions!

For a while, you have been able to set up alerts based on your functions and invocations. We are extending alerting capabilities with today's new feature. You can now set up an alert for your traces. With this new feature addition, you can set up alerts for the following cases:

  • When the duration of a transaction (composed of chain of invocations) exceeds a threshold.
  • When the origin Lambda function or any function in the transaction has errors
  • When the duration of the interaction between any specific resource exceeds a threshold. (For example; you can get notified when the duration of interaction for DynamoDB table with name "users" take more than 300ms)

And many more. In order to try the trace alerts, you can navigate to "Traces" page and save the query as an Alert Policy. Please let us know what you think about this feature and what do you want to see in Thundra next using the chat bubble at bottom right or by emailing to support@thundra.io.

Sampling support for .NET Agent

Thundra .NET agent now supports intelligent sampling so you can reduce your data usage. The agent provides you built-in samplers for Metrics, Traces and, Logs;

  • Count Aware Sampler
  • Time Aware Sampler
  • Error Aware Sampler
  • Duration Aware Sampler

You need to upgrade the agent version to 1.4.0 to use sampling. Documentations are here and the sample code is here. Come to our community slack and get instant help!

Weekly/Daily performance reports of your functions!

With this update, we are starting to send you weekly and daily performance reports of your functions! Reports include general metrics of your functions during the corresponding period, the problematic functions in terms of health and the most costly functions. You can choose the type of reports you want to receive under the profile settings page. Both weekly and daily reports are enabled by default.

HTTP instrumentation for .NET agent

.NET agent v1.3.0 has been released, and with this release, Thundra .NET agent supports HTTP instrumentation by default, no code change required. You can see the URL, path, query parameters, HTTP method type, HTTP response code, and the HTTP request in the span. What you can see is configurable as stated here.

Recent developments in .NET agent!

Thundra .NET agent v1.2.4 is released. Let's have a quick look at what features are in version 1.2.x:

  • Automated instrumentation for AWS services
    • SQS
    • SNS
    • Kinesis
    • Firehose
    • S3
    • DynamoDB
  • Improvements in OpenTracing API
  • Tag support to enrich the observability
  • Support for Serverless framework and SAM template

Check our documentation and come to our Slack and get instant support there.

Alerting is released!

Today, we are very glad to announce that we are introducing Thundra alerts. This feature is taking advantage of our flexible queries that you are already familiar of. Using alerts, you'll be able to stay on top of your serverless issues and will be able to maintain a peaceful serverless stack.

We defined default alert policies into your accounts checking the erroneous invocations. You may be receiving emails coming from this alert policy. You can use this as an opportunity to improve your system or creating more queries which fits to your use case more. All you need to do is saving a query as an alert policy and stay on top of your problems.

You can catch more details from our documentation: https://docs.thundra.io/docs/alerts-page. Please come to our Slack and get instant support there.

Node.js agent version 2.5.1 release!

We have released the version 2.5.1 of Thundra's Node.js agent and the version 14 of the corresponding layer. This new release introduces IORedis integration and also fixes the some problems related to the webpack by replacing webpack with rollup.js.

Check out for more information:

- NPM

- GitHub

Python agent version 2.3.4 release

We have released the new python agent version 2.3.4 and layer version 11. The new version includes AWS Athena integration so now you can trace Athena calls and get detailed information.

In the new release we added configuration option for http path depth seen in architecture view and traces. You can checkout the configuration page for more information about configuration variables for python.

The new release also includes an improvement regarding API Gateway call visualizations on architecture and traces pages by showing API Gateway nodes with path parameters.

Checkout for more information:

- Pypi

- Github