Hi everyone, 

I hope each and every user of us are healthy and safe in these unprecedented times. While we are working from home, we continue delivering new improvements for Thundra. 

We're so happy that some of you are already using the function and invocation tags extensively to enrich Thundra observability data with your business context. (See this blog for reference). In order to make the usability of tags in Thundra even easier, we've added a new navigation improvement. From now on, you can search the invocations and functions by clicking on a tag when you see it in function or invocation details.

In the invocation below the tag named "http_status" is set to 202. 

Clicking on this tag will filter all the functions of "blog-site-dev-postBlogPost". In this way, you can filter out all the other occurrences of the same business logic automatically. 

To learn how to use tagging, please consult to the documentation for Node.js, Python, Java, Golang, and .NET.

Happy observability to you all!
Stay safe and healthy!

Hi everyone, 

I hope each and every user of us are healthy and safe in these unprecedented times. While we are working from home, we continue delivering new improvements for Thundra. 

As you know, we are listing all logs of all functions under the Logs section that can be reachable on the left panel.  Previously, search capabilities on this page were limited and you couldn't save the searches that you made even if you run a search once. In order to resolve these issues, we've improved our Logs page by adding a query bar powered by our query language and added the ability to save the queries.  

Now, you can run extensive queries on your logs and you can even make a free text search on the logs of your functions. Then, you can save this search to revisit fast when you need it again. 

Happy observability to you all!
Stay safe and healthy!

Hi everyone, 

I hope each and every user of us are healthy and safe in these unprecedented times. While we are working from home, we continue delivering new improvements for Thundra. 

As you may notice, you're capable of using a comprehensive query language in order to filter and sort your observability data on Thundra. However, this query language lacked an important feature and some of you have asked about adding it. We heard you and added this feature today. Now, you can add negations to your queries from Thundra console and query helper while filtering and sorting invocations, functions, operations, traces, and logs. 

For example, you can type the below query to filter out the Java functions while you're searching for functions. 

Runtime NOT java ORDER BY LastInvocationTime DESC

Same can be achieved in the query helper as below: 

Note that you can now set up new alerts by using this new addition to our query language. 

Happy observability to you all!
Stay safe and healthy!

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.

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.

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!

Lambda nodes on our Architecture view are now clickable similar to the edges drawn. When you click any Lambda node a window opens from the right hand side of the screen and shows related metrics to the clicked Lambda node. We will add this feature gradually to the other type of nodes shown on Architecture page. Keep on following Thundra product updates, cheers ;).

Hello, now you can easily follow up recent changes about Thundra from the Changelog menu on our sidebar.

Thundra's Logs page is improved by adding a new column called Function Name. Now you can filter your logs according to your functions.

We would also be happy to hear about your feedbacks.

P.S: Many more features are coming to Thundra i.e. you will see a bell icon on the sidebar in the following days.