--- title: "Configure alerts by site" canonical: "https://docs.aryaka.com/space/KNOW/1543182/Configure%20alerts%20by%20site" format: markdown --- You can configure alerts for each site in your network. Each site inherits its default settings from either the Default Site Policy or a custom site policy as described in View, edit, and create alert policies . Configuring alerts by site allows you to have one or more site that does not inherit the default or custom configuration from another policy. Each site's alert details page contains a read-only Source field that displays the name of the default or custom policy where the alert is currently inheriting its configuration, or the site name if the Alert by Site is configured. To ensure that no policy conflicts occur, the alert engine evaluates alerts as follows: If the site has an active Alert by Site configured, use this alert configuration. If the site does not have an active Alert by Site configured, but it is included in a custom site policy, use the custom policy alert configuration. If the site does not have an active Alert by Site configured and it is not included in a custom site policy, use the Default Site Policy alert configuration. To configure alerts by site Open the Sites: Alerts by Site 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 Config by Site in the Alert Management tile. The Sites: Alert by Sites page appears. It includes a table with each site in your network listed in a table row. Click the  site name for which you want to configure one or more alerts. The selected site's notifications page appears. It displays the following alerts, whether each is customized, 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—Any interface of the Standby ANAP at a site is down. Aryaka Bandwidth Usage—The site's bandwidth usage exceeds the configured threshold. ANAP LAN/FLAN Interface—Any 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 connection count has exceeded the configured threshold. DHCP Server—The site's DHCP server is down. ANAP M1/F1/FM1 Interface—The interface of the ANAP at a site is down. ANAP M2/F2/FM2 Interface—The interface of the ANAP at a site is down. ISP Bandwidth—Utilization of an ISP link has exceeded configured threshold. Cloud Security Connector—A Cloud Security Connector is 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. Click the  Expand  icon (far right of a 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 selected site's alerts page appears in edit mode. Edit the following fields as appropriate for an alert: Click the  Customize  toggle to enable the corresponding alert. The toggle appears in green. Ensure the  Active  toggle is enabled. When enabled, the toggle is green. Click one or more of the following Notification fields (when selected, the field 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 site alert is updated. Related topics View, edit, and create alert policies Configure alert notifications by user group View and manage alerts Alert details Related video Configure alerts by site