Alert types and parameters
Akamai Cloud Pulse supports two types of alerts: system alerts and user alerts. Together, they provide default monitoring for common service health conditions while allowing you to define custom alert behavior as needed. Most environments use a combination of system and user alerts to surface conditions requiring attention.
Alerts are currently in limited availability for the Databases service. Support for additional services is planned for future releases.
System alerts
System alerts are preconfigured alerts that automatically monitor common service health conditions and notify you when the alert condition is met.
A system alert:
- Triggers automatically when one or more pre-defined metric thresholds are met or exceeded
- Applies automatically to all entities associated with the service, with the option to manually include or exclude individual entities
- Sends alert notifications to all users with read/write access to the affected entity
User alerts
User alerts are configurable alerts that allow you to define monitoring behavior based on your specific operational requirements.
A user alert:
- Triggers automatically when one or more user-defined metric thresholds are met or exceeded
- Applies only to entities within your access scope, and requires that all selected entities belong to the same account
- Supports custom thresholds and evaluation that you define, including the metrics and dimensions used for evaluation
- Sends alert notifications to the users belonging to the notification channel that you select
Evaluation criteria
Evaluation criteria determine how metrics, thresholds, dimensions, and time windows are evaluated to decide when an alert is triggered. These criteria help ensure alerts are triggered only when meaningful conditions are met.
For more information about service-specific metrics and dimensions, see the metrics reference index, which links to service-specific metrics documentation.
Alert parameters
The following alert parameters are preconfigured for system alerts and configurable for user alerts:
| Parameter | Description |
|---|---|
| General Information | |
| Name | The name of the alert |
| Description | A brief description of the purpose of the alert |
| Service | The Akamai Cloud service to which the alert applies (for example, Databases) |
| Severity | The severity level assigned to the alert: info, low, medium, or severe |
| Scope | The level at which the alert applies: account, region, or entity |
| Region | The geographic regions included in alert evaluation when the scope is set to Region |
| Entities | The specific entities included in alert evaluation when the scope is set to Entity |
| Alert evaluation criteria | |
| Data field | The metric monitored by the alert (for example, CPU Usage) |
| Aggregation type | The statistical method used to aggregate metric values over time: sum, minimum, maximum, or average |
| Operator | The comparison operator used to evaluate the metric against the threshold: >, < , ≥, ≤, or = |
| Threshold | The value used to determine when the metric meets the alert condition, expressed as a percentage (%) |
| Dimension filter | An optional dimensional attribute used to refine or contextualize the metric data being evaluated (for example, filtering Databases CPU usage by node type) |
| Polling interval | The frequency at which the system evaluates the metric data: 5 minutes, 15 minutes, 30 minutes, or 1 hour |
| Evaluation period | The time window over which the metric condition must be met before the alert is triggered: 5 minutes, 15 minutes, 30 minutes, or 1 hour |
| Blip interval | The number of consecutive evaluations that must meet the alert condition before the alert is triggered |
Updated 5 days ago