You can now get notified about your Thundra alerts on VictorOps.

In order to use this new feature, please follow following steps:

1. Follow this guide to setup a rest endpoint integration.

2. After setup, copy the url to notify.

3. Go to VictorOps settings at Thundra console and paste the URL to notify to the field there.

4. Press Save and you're done!

Now, you can set up VictorOps as another notification channel for your current alert policies and for the new policies that you'll create.

Please let us know what you think about this integration and about your new feature requests using the chat buble bottom-right.

You can now get notified about your Thundra alerts on Pagerduty.

In order to use this new feature, please follow following steps:

1. In your Pagerduty account, navigate to the Configuration menu and select Event Rules.

2. Click on Incoming Event Source and then copy Integration Key field to clipboard.

3. Go to Pagerduty settings at Thundra console and paste the Integration Key to the field there.

4. Press Save and you're done!

Now, you can set up Pagerduty as another notification channel for your current alert policies and for the new policies that you'll create.

Note that to be able to configure event behaviour, you should create a new event rule on Event Rules page if you don't already have one. You can filter your Thundra events by setting client equals thundra condition if you would like to create a seperate rule for Thundra alerts. You can read about event rules in here.

Please let us know what you think about this integration and about your new feature requests using the chat buble bottom-right.

Last month, we came up with our alerting feature which enables Thundra users to stay on top of their serverless issues. You can now redirect the alerts to your Opsgenie account and you can set up escalation policies in your organization more flexibly!

In order to use this feature, you need to follow these steps:

1. In your Opsgenie application, go to the team that you want to set up the Thundra integration for.
2. Go to Integrations and press "Add Integration".
3. From the list filter for Thundra and click on it.
4. Copy the field "API Key" to clipboard.
5. Go to Opsgenie settings at Thundra console and paste the API Key to the field there.
6. Press "Save" and you're done!

Now, you can set up Opsgenie as another notification channel for your current alert policies and for the new policies that you'll create.

Please let us know what you think about this integration and about your new feature requests using the chat buble bottom-right.

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.

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!

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.

With this update, you will be able to deep dive into your traces with Thundra's advanced query capabilities. For example filtering transactions that has interaction with DynamoDB and its interaction duration is greater than 1000 ms may help to find out bottlenecks related to DynamoDB in your application. After finding out the related trace, you can easily see invocation details, metrics and logs related to that trace which will help you fix the problem.

You can search following aspects of your transactions with Thundra:

• application names
• erroneous traces & specific error types
• traces that are triggered by some external resource (SQS, SNS, ApiGateway)
• invocation tags and function tags.

There are more of them that you can utilize while searching your traces, please refer to our documentation for more details and you can read related blog post.

Please provide your feedbacks and feature requests to support@thundra.io or on our Slack channel.

With this update to Thundra console, you'll be able to filter and sort your AWS Lambda functions according to their health which unlocks you the ability to keep control your serverless architecture better. You'll also be able to set up alerts using health queries.

Ability to filter according to error count is a good way of understanding what may go wrong in your system. However, this might be misleading sometimes. For example; you can filter the functions which has 10 errors in last 1 hour and it can return some results. This might not be a big problem because function has over a million invocations and having 10 erroneous invocation can be acceptable. For this reason, there should be a way to query the functions according to health. You will be able to filter functions whose health diminishes. For example; you can query the functions whose health is less than 80% and sort them ascending with respect to health. Now, you have a way of understanding the functions with poorest health.

The biggest advantage of this update arises as the ability to save health queries as alerts. Now, you can set up an alert saying that "Notify me when the number of functions in the user service whose health is less than 95% becomes more than 5.". In this way, you don't need to keep track of the count of errors. You can focus on what really matters: Health!

Please provide your feedbacks and feature requests to support@thundra.io or on our Slack channel.

.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.

With a new addition to our query console, you can now share the queries with your colleagues to report an anomaly in your system or to share your insights.

In order to achieve this, you need to click on the `Share` button in the query console. This will copy a special URL to clipboard. When you open this URL in a separate browser window, you'll see that Thundra arranged the global time range at top-right to that specific interval and run the query.

Alternatively, you can share the queries just copying the URL from browser address bar. In this case, you can only share the query but not the time interval.

We're glad to answer one of the most wanted items in our backlog with this improvement. This update will foster the collaboration between the serverless teams with nice monitoring. Happy serverless-ing!