Cold Starts

Lambda cold starts can be undesirable in some circumstances. Especially if invocation demand is highly variable and unpredictable, cold starts tend to happen much more frequently.

With Dashbird Policy alerting system, you can monitor and set a threshold for a healthy and acceptable level of cold starts to each function, a group of Lambdas or all of them.

In the example below, we set a limit for 100 cold starts over a period of 10 minutes. In case our application goes above that limit, Dashbird will automatically send us an alert to investigate and take measures to minimize the impacts of cold starts.

Here is an article we published about how to solve Lambda cold starts.

Resource Usage

When a function starts consuming too much resoursed, either memory or execution time, it can be the sign of a problem developers need to tackle.

With Dashbird, we can set a policy to alert in case memory usage goes above 90%, on average, over a period of 5 minutes, for instance. Analogously, the same policy could be setup for execution time.


Managing Lambda costs is essential for applications running in production. Especially if you charge customers for services running on Lambda and its costs are the basis for your pricing structure.

Dashbird can alert you in case costs start to rise unexpectedly, allowing you and your team to act quickly and avoid a terrible surprise at the end of the billing cycle.

For example, we could set up an active alerting system when invocations start costing more than $0.01, on average, over a period of 15 minutes.

We aim to improve Dashbird every day and user feedback is extremely important for that, so please let us know if you have any feedback about our features and error handling! We would really appreciate it!


Can’t find what you’re looking for? We’d love to help. Send us a message through the chat bubble or email us.

No results found