Service Limits
Alerts
| Resource | Limit | Description |
|---|---|---|
| Daily Notifications per Alert | 2000 | The daily total number of triggering Alert Notifications for a single alert. |
| Segments per Alert | 10,000 | The total number of segments returned in a single alert query. For example, configuring an alert on (container_memory_usage_bytes) by (container) will result in deactivation of the alert if there are more than 10,000 containers returned by this query. |
Deactivated Alerts
The alerts that exceed service limits will result in alert deactivation. Alerts that are deactivated will be disabled by Sysdig and no longer evaluated until the user manually re-enables the alert. If usage thresholds continue to be exceeded, the alert will again be deactivated.
Segmentation Limit
The total number of entities that are returned when grouping a metric by one or more labels.
Discover Deactivated Alerts
When an alert is deactivated, all triggering alert events associated with the alert are also deactivated. An email notification containing the deactivation reason and a link to the deactivated alert is sent to all admin users and team managers.
Deactivated Alerts appear on the Alerts page in the summary widget. Additionally, a Sysdig Event is created whenever an alert is deactivated.
Fix Alert Deactivations
Deactivated due to the daily notification limit
- Refine the alert scope and segmentation before re-enabling the alert.
- Intentional and significant changes in the infrastructure can also cause large numbers of alerts to trigger. Check the infrastructure before re-enabling the alert.
If Alert is deactivated due to segmentation limit
- Refine the alert scope.
- Reduce segmentation in alert configuration.
- Intentional and significant changes in the infrastructure can also cause large numbers of alerts to trigger. Check the infrastructure before re-enabling the alert.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.