Monitoring platform for keeping systems up and running at all times.
Full stack visibility across the entire stack.
Detect and resolve any incident in record time.
Conform to industry best practices.
Ever wondered what’s under the hood of your neighbors’ car, the situation in their wallet or the configuration of their serverless stack?
Well wonder no more! Today we will bring you the statistics of Dashbird so you could compare your Lambda functions with others. Unfortunately, the car and the wallet thingy you should figure out on your own 🙁
Let’s start… (I hope you like charts)
Out of 3000+ active Dashbird users, the average AWS account has 123 functions in total.
Seems that we have some Node.js people here at Dashbird.
As expected, us-east-1 and eu-west-1 are trending regions in Dashbird. But the cool fact is that over half of the Dashbird accounts use more than one region and almost 10% more than three regions.
We compared the performance indicators of the Lambda functions per runtime. Take a look at the results below.
As we all know, Java takes lots of time to boot up, but once done it will operate like a charm.
Next time we will bring you the statistics of errors, coldstarts, invocations, cost etc. Stay tuned! Meanwhile, you can sign up for a Dashbird account here.
Today we are announcing a new, updated pricing model and the end of free tier for Dashbird.
In this article, we’re covering 4 tips for AWS Lambda optimization for production. Covering error handling, memory provisioning, monitoring, performance, and more.
In this article we’ll go through the ins and outs of AWS Lambda pricing model, how it works, what additional charges you might be looking at and what’s in the fine print.
Dashbird was born out of our own need for an enhanced serverless debugging and monitoring tool, and we take pride in being developers.
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.