
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. Review collected by and hosted on G2.com.
it's not a dislike, but I would like Dashbird to support other serverless AWS services in the future, ex. Timestream or Athena are not yet supported. Review collected by and hosted on G2.com.