February product updates. Anomaly detection, incident management and better UX

These past couple of months were a bit hectic and there’s a good reason behind that. We’ve set out to create a better experience for our users, and it’s exactly what we did! Besides making a lot of quality-of-life changes, we’ve introduced new features that we think, will increase the speed at which you’ll debug your applications and give you a whole new perspective on all things AWS Lambda.

We got carried away by building features and improving the application experience, that we forgot to announce the changes. Here are recent changes at a glance:

  • New lambda view
  • New invocation view
  • Metric based alerting
  • Error reporting

New lambda view

updated lambda view

The new view has separate charts for invocations, errors, duration, memory usage, and cost. On the metric panel, you can see the sparklines, which indicate what is happening over the selected period, and clicking on them opens up the chart in full size. Picking the period is more straightforward, there are only four options at the moment: 1 hour, 1 day, 7 days, and 30 days. The bottom part includes recent invocations, which can be filtered down to errors, retries, cold starts, or anomalies, and all the errors that have happened with this lambda.

New invocation view

invocations view

We’ve streamlined the function invocation view so instead of having a separate page for invocations, the invocation detail slides open from the right. You can still scroll around lambda’s invocations list and open up a new one quickly.



Now you can set up metric-based alerting for any lambda or project. Just open up policies view under alerting tab and start adding the conditions. Whenever a condition fails, an incident opens and stays that way until the term passes again. For every policy, you can attach multiple notification channels, which are shared within the organization account, so that you only need to define them once.

Errors View

errors view

Errors view got design updates and moved to policy-based notifications. You can choose which types of errors you want to receive for selected targets. We generated the default policies for you to receive all errors of all lambdas, but feel free to change it. At the moment we only send out notifications when a new error occurs, or it reopens. We recommend resolving the error after bugfix or mute it when it is not important.


  • Added Dashboard menu item for easier navigation. Clicking on the logo still works as well
  • Search and header have a new look and feel
  • API Gateways got a design overhaul
  • Logs now support JSON formatting

We’re an AWS Advanced Technology Partner

We’re happy to announce that we have been accepted as an Advanced Technology Partner at AWS and we are more than proud to be endorsed and have all our efforced recognized by the folks at AWS. More about this 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.