--- title: "View, edit, and create alert policies" canonical: "https://docs.aryaka.com/space/KNOW/1609065/View%2C%20edit%2C%20and%20create%20alert%20policies" format: markdown --- The Alert Policies page displays the predefined Default Customer Policy, the Default Site Policy, and any custom site policies you have created. Custom site policies initially inherit the default site policies, but can then be modified as to which sites in your network they apply to, and the conditions and configuration of the actual associated alerts. You can modify the Default Customer Policy but you cannot add customer policies. You can modify the Default Site Policy and add custom site policies. To view and edit the Default Customer Policy Open the Default Customer Policy if it is not already open: Log in to MyAryaka. The Home page appears. Click  Global Settings in the left navigation pane. The Global Settings page displays a series of tiles. Click Alert Policies in the Alert Management tile. The Alert Policies page appears. Click the  Default Customer Policy tile. The Default Customer Policy page appears. It displays the following default alerts, whether each is active or disabled, and the notification details for the service (in the current read-only mode, the notification is on when the field is gray and off when it is white). All alerts are turned on by default. SmartCDN Usage Cost—Total SmartCDN usage for your Bill to Date is greater than or equal to 95% of the $ Commit for a specific Quote. Certificate Authority Config—The certificate authority is not configured.  Users Count—Unable to fetch user data. Certificate Authority Expiring—The certificate authority is expiring soon or has expired.  Private Access Bursting—For a specific region, you are experiencing bursting usage. Connection to Identity Management—The connection to the identity management server is down.  Oversubscription—A specific SKU is experiencing usage beyond the subscribed bandwidth. Certificate Expiry—Certificate used for SSL proxy has expired or is about to expire. Inter-region Usage—A region is experiencing high inter-region usage. Groups Count—Unable to fetch user group data. Concentrator Bursting—Aryaka's Smart Access Concentrator (SMAC) for a specific region is observing bursting usage. Region Bursting—A region is exceeding its subscribed bandwidth as the result of bursting. Click the Edit  icon. The Default Customer Policy page appears in edit mode. Edit the following fields as appropriate: Click the Active toggle to enable or disable the corresponding alert. When active, the toggle is green. Click one or more of the following Notification options (when selected, the option is green): Notify when the alert is generated Notify when the alert is resolved Notify during business hours only Click Dampen if you want the alert email notifications to be sent as follows: If there are three alerts during a two hour period, do not send any additional notifications of the alert for next 24 hours (from the time of the third alert). The third alert notification includes a note that warns: You will not receive any additional notifications for the next 24 hours. (Certificate Expiry alert only) Click the Expand icon at the far right of the Certificate Expiry row. The Minor, Major, and Critical fields appear. These fields each include a default value that determines when an alert is generated and sent for each severity. (Certificate Expiry alert only) Edit the default values in one or more of the Minor, Major, and Critical fields.  Click Submit . A message prompts you to confirm that the policy configuration takes effect immediately. Click OK . The Default Customer Policy is updated. To view and edit the Default Site Policy Open the Default Site Policy if it is not already open: Log in to MyAryaka. The Home page appears. Click  Global Settings in the left navigation pane. The Global Settings page displays a series of tiles. Click Alert Policies in the Alert Management tile. The Alert Policies page appears. Click the  Default Site Policy  tile. The Default Site Policy page appears. It displays the following default alerts, whether each is active or disabled, and the notification details for the service (in the current read-only mode, the notification is on when the field is white, and off when it is gray): Edge Retransmission—TCP retransmission from Aryaka's POP to the site has exceeded the configured threshold. Site Bursting—A site in specific region is experiencing bursting. POP Primary - Loss—The primary path from Aryaka's POP to the site is experiencing packet loss. POP Secondary - Loss—The secondary path from Aryaka's POP to the site is experiencing packet loss. DHCP Relay—The site's DHCP relay is down.  POP Secondary - Latency—The secondary path from Aryaka's POP to the site is experiencing high latency. POP Primary - Latency—The primary path from Aryaka's POP to the site is experiencing high latency. Standby ANAP LAN/FLAN Interface—The LAN or FLAN interface of the standby ANAP at a site is down. Aryaka Bandwidth Usage—The site's VPN Path Aryaka bandwidth has exceeded the configured threshold. ANAP LAN/FLAN Interface—The LAN or FLAN interface of the ANAP at a site is down. Internet Health—The ISP link connected to the ANAP at the site is in bad or degraded state. ANAP Provisioning Server—The active ANAP at site is unable to establish connectivity to Aryaka Provisioning Server required to manage the ANAP. Connections—The site's VPN Path Aryaka Connection count has exceeded the configured threshold. DHCP Server—The site's DHCP server is down. ANAP M1/F1/FM1 Interface—One or more M1/F1/FM1 interfaces of the ANAP at a site are down. ANAP M2/F2/FM2 Interface—One or more M2/F2/FM2 interfaces of the ANAP at a site are down. ISP Bandwidth—Utilization of an ISP link has exceeded configured threshold. Cloud Security Connector—One or more of the cloud security connector tunnels are down. DHCP Pool—The site's DHCP server is low on available IP addresses to lease to DHCP clients.  Cloud Transport Connector—One or more of the cloud transport connector tunnels are down. POP Primary - Tunnel—The primary IPsec tunnel from the site to Aryaka's POP is down. POP Secondary - Tunnel—The secondary IPsec tunnel from the site to Aryaka's POP is down. Site to Site Tunnel—The site-to-site tunnel configured on the ANAP is down. Standby ANAP Provisioning Server—The standby ANAP at site is unable to establish connectivity to Aryaka Provisioning Server required to manage the ANAP. POP - Tunnel—Both primary and secondary tunnels from the site to Aryaka's POP is down. (Optional) Click the Expand  icon (far right of each row) to display additional read-only details about the service. For example, the ANAP M1/F1/FM1 Interface displays the alert thresholds that determine when an alert is generated and sent for each severity (minor, major, or critical). Click the Edit  icon. The Default Site Policy page appears in edit mode. Edit the following fields as appropriate for an alert: Click the Active toggle to enable or disable the corresponding alert. When active, the toggle is green. Click one or more of the following Notification options (when selected, the option is green): Notify when the alert is generated Notify when the alert is resolved Notify during business hours only Click Dampen if you want the alert email notifications to be sent as follows: If there are three alerts during a two hour period, do not send any additional notifications of the alert for next 24 hours (from the time of the third alert). The third alert notification includes a note that warns: You will not receive any additional notifications for the next 24 hours. Click the Expand + icon at the far right of a row. The Minor, Major, and Critical fields appear. These fields each include a default value that determines when an alert is generated and sent for each severity. Edit the default vales in one or more of the Minor, Major, and Critical fields.  Click Submit . A message prompts you to confirm that the policy configuration takes effect immediately. Click OK . The Default Site Policy is updated. To create a custom site policy Open the Alert Policies page if it is not already open: Log in to MyAryaka. The Home page appears. Click  Global Settings in the left navigation pane. The Global Settings page displays a series of tiles. Click Alert Policies in the Alert Management tile. The Alert Policies page appears. Click the  Add New  tile in the Site Policies section. The Add Alert Policy page appears with the Policy and Sites tab page displayed by default. Enter a policy name and description in the appropriate fields. It is recommended to reference the sites, geographic region, or issue you are trying to address with this custom policy in the description. Add one or more sites to the policy: Click Add Sites in the Sites pane. The Add Site dialog appears. It displays all of the sites in your network. Do one of the following: Click the row of each site you want to add. The row turns green and displays a check at the right of the row. Click Select All , then click any unwanted rows to remove them from the selection. Click Add Selected . The selected sites are added to the policy and appear in the table in the Sites pane of the Add Alert Policy tab page. Click the Alerts  icon. The Alerts tab page appears. It displays the following fields and controls for each alert type: Customize toggle—Disabled for every alert by default. Active toggle—Enabled by default for certain alerts and disabled for others. Custom policies inherit attributes from the Default Site Policy, so if the alert is active in the default policy, it is active by default in the custom policy. Name—The service or device with which the alert is associated. Notification options—Defines when the alert is sent. Expand + icon—Appears at the far right of every row. When clicked, it displays the Trigger Threshold fields where you configure the alert thresholds that determine when an alert is generated and sent for each severity (minor, major, or critical). Customize the alert for the selected sites as follows: Click the Customize toggle for the alarm you want to customize. Click the Active toggle for the alarm if it is not already on. Click one or more of the following notification options (when selected, the option is green): Notify when the alert is generated Notify when the alert is resolved Notify during business hours only Click Dampen if you want the alert email notifications to be sent as follows: If there are three alerts during a two hour period, do not send any additional notifications of the alert for next 24 hours (from the time of the third alert). The third alert notification includes a note that warns: You will not receive any additional notifications for the next 24 hours. Set the trigger thresholds for this alert: Click the Expand icon (at the right of the row). A description of the threshold and the Minor, Major, and Critical fields appear. These fields each include a default value that determines when an alert is generated and sent for each severity. (Optional) Edit the default values as appropriate. Note that the minor value must be the smallest, and the critical value must be the largest. Click Submit . A message prompts you to confirm that the policy configuration takes effect immediately. Click OK . The policy is created and appears in a tile in the Site Policies section of the Alert Policies page. Related topics Configure alerts by site Configure alert notifications by user group View and manage alerts Alert details View and edit business hours Related videos Configure custom alert policies for a site