Dashbird supports full-fledged and customisable failure detection and incident management for serverless applications. Incidents are divided into two main sub-categories: execution errors and metric condition failures. This article is about metric alerts. You should also learn about handling execution errors.
Metric incidents are custom condition violations of a user-selected metric. For example, you can configure an alert for each time a Lambda function takes more than a second to execute.
To configure your first alert policy, navigate to -> Policies -> + ADD.
Alert policies consist of one or more metric conditions and one or more notification channels.
A notification channel is a way to notify user of the failures (slack integration or e-mail address). Read more about notification channels.
A metric condition consists of:
You can choose to open an incident per policy, condition or target.
Alerting should be an ongoing process, we reccommend testing different policies, adding new ones based on needs and deleting/muting unnecessary alerts to avoid alarm fatique.
Can't find what you're looking for? We'd love to help. Send us a message through the chat bubble or email us.