With Anomaly detection you can configure Triggers to send notifications when a metric value goes over, or dips below, a threshold. For example: When the error rate of an application goes over 5 % or free memory dips below 100MB.
Anomaly detection works by detecting changes in metric values on a minutely basis. When a threshold condition is reached we will notify you of the new alert created by this event, and we'll notify you again when the situation no longer occurs.
Sometimes it's good to know immediately when a threshold is reached, at other times it may be good to wait a few minutes before alerting you. For this you can use warm-ups and cooldowns.
Alerts can have four different states:
- Warming up means that this Alert is in its warm-up phase. You can configure this per Trigger. It allows you to wait for a condition to be true for a few minutes before you get alerted.
- Ongoing means that this Alert is active. Its threshold condition is currently reached.
- Cooling down means that an Alert is not over the threshold condition anymore, but will not be closed until the cooldown duration is over. If it reaches its threshold again within the cooldown period, it will move back to the "ongoing" status.
Closed means the Alert is not ongoing and not in the cooling down period. We don't call them "solved" because you still might want to look at what happened here.
After you've configured notifications, you will be notified when an alert goes into the ongoing phase, for reminders you set up during that phase, and when it's closed again.
In each email you receive about any alert, we'll send you a full overview of all your alerts. You'll see an overview of new alerts, reminders, ongoing alerts and closed alerts.
Anomaly detection can be configured per app in the "Anomaly detection" section in the app navigation. By default you will see the latest alerts created by triggers that you've configured for the app.
In the top navigation you can switch to the triggers page to create new and edit existing triggers.
Triggers can be configured for a variety of metrics, such as, but not limited to:
- Error rates
- Error (absolute) counts
- App throughput
- Performance of actions (slow actions)
- Queue time
- Host metrics
- CPU load
- Disk I/O
- Disk usage
- Load averages
- Memory usage
- Network usage
Created Alerts are based on a certain threshold condition from a Trigger. When the Trigger configuration changes, the linked alerts no longer match with the parent Trigger. For this reason it's not possible to directly edit a Trigger's configuration.
Instead, when editing a Trigger, a new Trigger with the new configuration is created while the old Trigger and its linked Alerts are archived. Currently, archived Triggers and Alerts are not visible in the AppSignal web interface.
Warm-up and cooldown settings can be configured on a per Trigger basis. The setting allows you to configure the amount of minutes the system waits before opening an Alert and closing it.
When a threshold condition is met an Alert is opened, e.g. the error rate is higher than 5%.
When a warm-up duration is configured for a trigger it will wait with notifying you until after the warm-up time has passed. The threshold condition needs to be met for the entire warm-up duration before the alert is opened. The alert in warm-up is immediately closed if the condition is no longer met during this time.
Alerts that have only entered the warm-up phase are visible in the AppSignal web interface, but no notification will be send for these alerts.
When an Alert is opened by a Trigger it will automatically close when the Trigger threshold condition is no longer reached. When the threshold is reached again it will open another Alert. This may result in more notifications than wanted.
In order to not get overwhelmed with notifications about a Trigger threshold condition that constantly dips below and above a certain value you can use Trigger cooldowns.
Triggers with cooldowns wait for the specified amount of time in minutes before closing an Alert. When it doesn't occur again in the cooldown time the Alert is finally closed. If it does occur, the Alert is reopened without an explicit notification.