Dashbird announces incident management platform

Since the beginning of Dashbird, we’ve been conducting user interviews with all the users that take the time to jump on a call with us. One of the most common requests we get is the ability to customise alerts – specifically, what failures you will get notified upon and the ability to set custom alert based on metrics. Today we announce a new part of Dashbird that takes care of that – an incident management platform.

If you haven’t yet tried Dashbird, it’s an observability platform for serverless applications that helps you build applications with less time and increase the quality of your service. Take it for a spin in 5 minutes with no code changes.

Dashbird detects all excecution and configuration errors by importing logs and smart pattern matching them against failure patterns. With Dashbird, you’ll not only be able to tell that something is not working, you’ll be able to say WHAT exactly went wrong. The powerful thing about log-based error detection is that it automatically covers all the functions under your account without any implementation overhead.

Setting up alerts for execution failures

The first thing we redid was the exception handling logic – now you can specify exactly what function or service you want to get alerted about and which are not so important. We also support granularity for the error type. For example, you can get only CRASH type exceptions, and not timeouts or out of memory errors. By default, users will get email alerts about all failures that happen after they sign up.

Metric alerting and incident management

Dashbird now supports setting alerting conditions for all Lambda metrics. The supported metric types can contain invocations, cold starts, errors and retrys and of those you can monitor the count, latency, memory usage, cost etc. Metric alerting can be a powerful way of getting in front of performance and cost issues. Imagine you can set an condition for all customer-facing functions to be executed in less than 500ms.

For the future

Our aim for the alerting section of Dashbird is to make it configurable for almost any event a user can think of for alerting. Another area where we are looking to improve is our notification channel support. Currently we support Slack and email integration, but webhooks support and an open API is on the roadmap.

Start now

In case you’re looking to introduce metric alerting to your company, we usually only recommend customers to start with a few basic metrics and build on top of those. Building and managing alerting rules should be an ongoing process and we’re happy to get you started. Our experts are happy to help with a consultation for setting up alerts.

To get the process going, you could either sign up for Dashbird and we’ll take it from there or schedule a demo here.

Read our blog

Introducing easy custom event monitoring for serverless applications.

Today we are excited to announce scheduled searches – a new feature on Dashbird that allows you to track any log event across your stack, turn it into time-series metric and also configure alert notifications based on it.

Why and How to Monitor Amazon OpenSearch Service

One of the most vital aspects to monitor is the metrics. You should know how your cluster performs and if it can keep up with the traffic. Learn more about monitoring Amazon OpenSearch Service.

Why and How to Monitor AWS Elastic Load Balancing

Dashbird recently added support for ELB, so now you can keep track of your load balancers in one central place. It comes with all the information you expect from AWS monitoring services and more!

More articles

Made by developers for developers

Dashbird was born out of our own need for an enhanced serverless debugging and monitoring tool, and we take pride in being developers.

What our customers say

Dashbird gives us a simple and easy to use tool to have peace of mind and know that all of our Serverless functions are running correctly. We are instantly aware now if there’s a problem. We love the fact that we have enough information in the Slack notification itself to take appropriate action immediately and know exactly where the issue occurred.

Thanks to Dashbird the time to discover the occurrence of an issue reduced from 2-4 hours to a matter of seconds or minutes. It also means that hundreds of dollars are saved every month.

Great onboarding: it takes just a couple of minutes to connect an AWS account to an organization in Dashbird. The UI is clean and gives a good overview of what is happening with the Lambdas and API Gateways in the account.

I mean, it is just extremely time-saving. It’s so efficient! I don’t think it’s an exaggeration or dramatic to say that Dashbird has been a lifesaver for us.

Dashbird provides an easier interface to monitor and debug problems with our Lambdas. Relevant logs are simple to find and view. Dashbird’s support has been good, and they take product suggestions with grace.

Great UI. Easy to navigate through CloudWatch logs. Simple setup.

Dashbird helped us refine the size of our Lambdas, resulting in significantly reduced costs. We have Dashbird alert us in seconds via email when any of our functions behaves abnormally. Their app immediately makes the cause and severity of errors obvious.