Documentation
About Alerts
This topic provides an overview of alerts. It also includes information about the severity of the alerts and type of the alerts.
Overview of alerts
Alerts are the notifications that Phoenix generates to provide pertinent information about an event or an exception situation. For example, if the cloud storage utilization crosses the 80% limit, Phoenix creates an alert. Phoenix creates an alert for specific events, or for every occurrence of an exception. The alerts appear under the Alerts tab on the Alerts page.
An alert stays active until it is resolved and appears in the Alerts list. After fixing the event or exception that caused the alert, Phoenix treats the associated alert as resolved, and the alert no longer appears on the menu bar of the Dashboard or the Alerts list. A record of active alerts, as well as resolved alerts, appears in the Alerts History report. For more information, see Reports.
By default, all Phoenix administrators, such as cloud administrators, organization administrators, and group administrators, are subscribed to alerts. However, they can unsubscribe themselves to the alerts using the My Subscriptions tab on the Alerts page. Additionally, the cloud and organization administrators can manage alert subscriptions for the non-administrators. Based on the subscriptions, non-administrators receive email notifications in the event of job failures, reports, and so on.
Severity of alerts
The alerts that Phoenix generates can assume either of these levels of severity: Critical, Warning, or Information. The severity of the alerts usually indicates the priority for a resolution of the underlying event or exception. The following table provides details about the severity of the alerts:
| Severity of alert | Description |
| Critical | Indicates a state that requires immediate resolution. |
| Warning | Indicates a state that requires resolution as soon as possible. However, the priority of alert resolution is lower than that of the critical alert. |
| Information | Indicates that the event may not require administrator-assisted resolution. Alerts of this severity are only informative. |
Types of alerts
The following table lists the alerts that Phoenix generates.
| Alert | Alert type | Created when | Severity | Resolved when |
|
License Expired (Expiry date:month dd yyyy) |
License |
The Phoenix license expires. |
Critical |
You renew the Phoenix license.
|
|
License About to Expire (Expiry date:month dd yyyy) |
License |
The Phoenix license is scheduled to expire after 30 days. |
Warning |
You renew the Phoenix license.
|
|
Backup failed |
Jobs |
The backup job fails. |
Warning |
Not resolved.
|
|
Backup window expired |
Jobs |
Phoenix does not back up the entire data set within the specified duration and does not create a restore point. |
Warning |
Not resolved.
|
|
Backup success with errors |
Jobs |
The backup is successful but with errors. |
Information |
Not resolved.
|
|
Restore failed |
Jobs |
The restore fails. |
Critical |
Not resolved.
|
|
DR failed |
Jobs |
The triggered disaster recovery job fails. |
Warning |
Not resolved.
|
|
Defreeze starts for snapshot |
Jobs |
The user clicks Defreeze for a cold snapshot on the Restore Data page.
|
Information |
Resolved when defreeze activity completes. |
|
Defreeze done for snapshot |
Jobs |
Phoenix completes the defreeze activity for a cold snapshot.
|
Information |
Auto-resolved in 3 days, that is, the number of days the snapshot remains thawed. |
|
Folder(s) misconfigured for backup |
Jobs |
The backup job is triggered and the folder specified during the backup is missing.
|
Warning |
Resolved when the next backup job is triggered. |
|
Pre-script execution failed |
Jobs |
The pre-backup script execution fails. |
Information |
Auto-resolved in 7 days. |
|
Post-script execution failed |
Jobs |
The post-backup script execution fails. |
Information |
Auto-resolved in 7 days. |
|
Upload logs success |
Jobs |
The user clicks Request Job Logs on the Job Details page and Phoenix successfully uploads logs to the server. |
Information |
Not resolved.
|
|
Upload logs failure |
Jobs |
The user clicks Request Job Logs on the Job Details page and the logs fail to get upload on the server. |
Information |
Not resolved.
|
|
Configuration rule invalid |
Configuration |
|
Warning |
Resolved when,
|
| Auto discovery cron job failed | Configuration | When Phoenix cannot auto-discover SQL instances or availability group on the server due to the failure of the cron job. | Warning | Resolved when the auto-discovery succeeds on the node. |
| Different client versions for AG Nodes | Configuration | When Phoenix discovers the different client versions of the nodes hosting the availability group. | Warning | Resolved when the client version of the nodes hosting the availability group is upgraded to the same version. |
|
CloudCache storage space low |
CloudCache |
The CloudCache utilization exceeds 80% but is less than 100%. |
Warning |
CloudCache storage utilization falls below 80%. |
|
CloudCache Storage Space Full |
CloudCache |
The CloudCache utilization exceeds 100%. |
Critical |
CloudCache storage utilization falls below 100%. |
|
CloudCache not reachable for server |
CloudCache |
If a server cannot connect to CloudCache during backup or restore job. |
Warning |
When the server connects to CloudCache in the subsequent backup or restore job. |
|
CloudCache decommission started |
CloudCache |
The user clicks Decommission Cache for the respective Phoenix CloudCache. |
Information |
When the Decommission CloudCache activity completes for the respective Phoenix CloudCache. |
|
CloudCache decommission completed |
CloudCache |
The decommission CloudCache activity for the respective Phoenix CloudCache is completed. |
Information |
Not resolved.
|
|
Upgrade to version<x.x::revision number> failed |
Upgrade |
If the upgrade fails. |
Warning |
Not resolved.
|
Note: The Jobs alerts will be automatically removed from the Alerts list after 7 days.