Dashbird has been a lifesaver for me. Debugging and capturing errors is hard with a fully cloud-native serverless deployment. That's why you need a tool like Dashbird to make it easier and faster for you. I primarily use Dashbird to show me if I've got any unexpected/unknown errors or what their error count is. It's good to see it reporting and giving me a heads up on things that are not tagged, things that could be upgraded, things that are orphaned.

You could, in theory, achieve a similar outcome by using CloudWatch, but you would have wasted so much of your development time. By using Dashbird, you no longer have to think about configuring an SNS topic to send a notification on failure or switch between tens of different CloudWatch log groups. As a developer, you can think of Dashbird as a productivity tool that will save you time and make any microservice architecture a much easier sell when talking to IT managers worrying about how to monitor all the small "moving parts" in the serverless microservice ecosystem.

Dashbird gives an easy view and access to my lambda functions and api gateways. The alerting functionality is great and it is very easy to view the execution logs. Also there is a straight link to Cloudwatch logs so it is much easier to find the log group if AWS logs are needed. Customer support is also excellent. Setting up the service was easy because it only required an installation of a Cloudformation Stack.