No matter how skilled is the observability tool we have, we never want to sit behind a computer and check if our systems are functioning well, right? Thundra is that skilled observability tool with unique features such as full tracing, trace search for programming languages Node.js, Python, Java, .NET, and Golang. We then thought that how can we minimize the time you need to spend with Thundra while keeping your operational excellence maximized. For this reason, we recently came up with flexible alerting that enables you to build up the alerts that you need. It’s better to prevent issues before they actually happen. For this reason, we’re introducing periodic reports today to keep you updated about the performance and health of your serverless stack.
With this new addition to our features, serverless developers will receive reports daily and weekly about the performance of their system. When you first see the report from top to bottom you’ll see the high-level metrics as below. This gives an initial idea if there’s something problematic there.
Hope you’ll never see something that will urge you to check the rest of the report and Thundra console immediately but when you need, the rest of the report has necessary items detail.
Problematic functions section lists the function with the poorest health. Using that, you can prompt the people who can have a closer look at these functions by just clicking on the function name. You can then have the opportunity to understand why by working on trace charts and transactional maps of distributed applications.
Even when everything seems healthy, you may be losing money because your functions are getting invoked so frequently because of a wrong configuration (or maybe luckily due to the traffic you’ve dreamed for) or there’s something wrong in the function (bad coding practice, slower third-party APIs, etc) that can make your app run slower and so more expensive. Thundra lets you know about these costly functions as well, like below.
For both categories, you can click on the category title to see all the functions sorted with respect to health or cost in the functions’ list.
To conclude, we believe this is a first nice step to keeping our customers informed even if they’re not checking Thundra console. We are thinking of some further improvements to our reports such as configuring reports according to projects, adding distributed traces to the report with a histogram and some more. If you also have some brilliant ideas that can make a periodic report better just reach us via email@example.com, or on Twitter @thundraio, or join our Slack and let’s chat. You can sign up to Thundra or see live demo to see Thundra in action.
Originally published at https://blog.thundra.io.