Announcing: Multiple AWS Account Support And Webhooks

We just released two new features at Dashbird. Starting now, you can connect more than one AWS account to your Dashbird account and you can also start integrating Dashbird with other tools in your workflow via Webhooks.

Multiple AWS Account Support

Often times, teams use more than one AWS account in their development setup. For instance, production and development stages can be deployed under different accounts to prevent accidents and restrict production access. Still, both accounts will require Dashbird and navigating between accounts was a drag until now. Starting today, you can onboard multiple AWS accounts inside the app. Here are more detailed instructions.


As developers ourselves, we understand how important it is to automate workflows and integrate services with each other to plan and collaborate more effectively. This is why we built webhooks to Dashbird.

Dashbird supports sending webhooks on multiple events. You can send a webhook for every error occurence or if something changes in the status of an error (like it gets resolved or re-surfaces). Here’s the full overview of how webhooks work in Dashbird.

Integrating with third-party services

Launching webhooks will be the first step towards integrating Dashbird into your development workflow. In the following weeks we will release Zaps and feature that make it easier to integrate Dashbird with JIRA and other bug ticketing systems.

We advise routing webhooks through Zapier.

What’s next

We have a ton of interesting stuff coming in the next months. Here’s a public roadmap where you can see what we are currently working on.

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.