For example, consider that a Customer has configured the Link Down alert delay for 2 minutes. If a WAN link loses communication with the Edge, Operator Alerts are sent immediately. Enterprise Alerts are sent after a delay of 2 minutes.

1. In the Alert Configuration window, the Alerts tab is displayed by default.

   
   

2. Configure the Notification Settings as required.
3. Under the Incident section, select the check boxes as required, and enter the corresponding Notification Delay time in minutes.
   Note:

   • The On/Off toggle button is automatically set to On if all the events are selected.
   • Hover over the information icon next to each event for more information.
   • You can use the event ALERT_CONFIGURATION_UPDATED to filter the events triggered by changes to the Enterprise Alert configurations.
4. Expand Email/SMS in the Notifications section to display the contact details of existing admin users.

   

5. Following contact details are displayed:

   Table 1. Contact Detail Option Descriptions

   Option	Description
   Name	This field is auto-populated based on the configured administrators.
   Role	Displays the role of the corresponding admin user.
   Email Address	Displays the email address of the corresponding admin user.
   Phone No	Displays the phone number of the corresponding admin user.
   Email	Activate the toggle switch to send email notification to the admin user's email address.
   SMS	Activate the toggle switch to send SMS notification to the admin user's mobile number. Note: This option is available only if the admin user has a valid phone number.
   Verify	Select to validate the email address and/or phone number of the user.

6. The following additional options are available:

   Table 2. Additional Option descriptions

   Option	Description
   Add Receiver	Selecting this option creates a new row for the admin user. Enter the name and phone number.
   Add Multiple Emails	Select this option to add multiple email addresses for the admin user. The email addresses must be added in a comma separated list.
   Delete	Select this option to delete all the contact details of the selected admin user.

7. Expand Configured Hosts under Select Configured SNMP Trap Destination(s) to display the configured SNMP Traps. You can select one or multiple traps using the drop-down menu.

   

   Note: If no SNMP Trap is configured, this section displays a link to the SNMP Traps page.
8. Expand Configured URL under Select Configured Webhooks to display the configured webhooks. You can select one or multiple webhooks using the drop-down menu.

   

   Note: If no webhook is configured, this section displays a link to the Webhooks page.
9. Select Save Changes.

Following fields are available under v2c SNMP Trap Destinations:

Table 3. v2c SNMP Trap Destinations Option Descriptions

Option	Description
Hostname/IP Address	Enter the IP address.
Port	Enter the port number.
Community	Enter the community. Community can be private or public.
Verify	Select this option to validate the IP address.
Add Destination	Select this option to add a new v2c SNMP Trap Destination.
Delete	Select this option to remove the selected entry from the table.

Following fields are available under v3 SNMP Trap Destinations:

Table 4. v3 SNMP Trap Destinations Option Descriptions

Option	Description
Hostname/IP Address	Enter the IP address.
Port	Enter the port number.
Username	Enter the username.
Authentication	Select one of the following: MD5 SHA Displays Disabled by default.
Encryption	Select one of the following: DES AES Displays Disabled by default.
Verify	Select this option to validate the IP address.

The Webhooks page in the Alert Configuration window, allows you to configure the following details:

Table 5. Webhook Alerts Option Descriptions

Option	Description
URL	Enter a valid HTTPS URL. This serves as the target application for the webhooks.
Code	Enter an expected HTTP response status code for each webhook recipient. By default, the Orchestrator expects webhook recipients to respond to HTTP POST requests with a status code as HTTP 200.When Orchestrator receives an unexpected status code from a recipient server or a proxy server, it considers that the alert delivery has failed, and generates an ALERT_DELIVERY_FAILED customer event. This event helps to identify when a webhook recipient server may fail to function as expected.
Secret	This field is optional. Specify a secret token for each configured webhook recipient, which is used to compute an HMAC for each webhook request sent to the corresponding recipient. The HMAC is embedded in a X-Webhook-Signature HTTP header, along with a version parameter, which identifies the signature algorithm and a timestamp. X-Webhook-Signature: v=<signature-version>&t=<timestamp>&s=<hmac> The recipient interprets the components as follows: v: Version of the algorithm used to produce the signature. The only supported value is 1. t: Millisecond-precision epoch timestamp corresponding to the time at which the request is issued. s: HMAC computed by Orchestrator. The HMAC is computed as follows: HMAC-SHA256(request-body + '.' + timestamp, secret). The message used to compute the HMAC is formed by concatenating the request body, a single period, and the value of the timestamp parameter that appears in the signature header. The specific HMAC algorithm used to produce the code is HMAC-SHA256.After receiving a Webhook request, the listening server can verify the authenticity of the request by computing its own HMAC-SHA256 signature according to the same algorithm and compare the newly-computed signature with the one generated by the Orchestrator.
JSON Payload Template	This is a required field. Orchestrator delivers alert notifications to each webhook recipient, through a JSON payload contained within the body of an outgoing HTTP POST request. Orchestrator generates payload content dynamically, as notifications are sent by performing variable interpolation. The supported placeholder variables in the user-configured payload template are replaced with alert-specific values.
Verify	Select this option to validate the entered details.

Select Configure Payload Template link under the JSON Payload Template option to configure the following:

Table 6. Payload option Descriptions

Option	Description
Alert Time	Enter the date and time at which the alert must be triggered.
Alert Type	Select the type of alert from the drop-down menu. By default, it is displayed as N/A.
Customer Logical ID	Enter the logical ID of the customer to whom the notification must be sent.
Customer	Enter the name of the customer to whom the notification must be sent.
Device Logical ID	Enter the logical ID of the Edge to which the alert must be applied.
Device Description	Enter a brief message describing the Edge to which the alert must be applied.
Device Serial Number	Enter the serial number of the Edge to which the alert must be applied.
Device Name	Enter the name of the Edge to which the alert must be applied.
Last Contact	Enter the date and time at which the affected Edge most recently communicated with the Orchestrator. This is applicable only for the Edge alerts.
VCO	Enter the Hostname or public IP of the Orchestrator from which the notification must be sent.
Message	Enter a brief message describing the event that must trigger the alert.
Entity Affected	Enter the name of the entity: Edge or link or VNF, to which the alert must be applied.

The following example shows a sample JSON payload template:

{
"alertTime": "alertTime",
"alertType": "alertType",
"customer": "customer",
"customerLogicalId": "customerLogicalId",
"entityAffected": "entityAffected",
"deviceLogicalId": "deviceLogicalId",
"lastContact": "lastContact",
"message": "message",
"vco": "vco",
"deviceName": "deviceName",
"deviceDescription": "deviceDescription",
"deviceSerialNumber": "deviceSerialNumber"
}

To configure custom events to be delivered as alerts, perform the following steps:

1. In the SD-WAN service of the Enterprise portal, select Service Settings > Alerts & Notifications . The Alert Configuration screen appears.

   

2. Select Incident > Events > + Select Events . The Events page appears.

   

3. In the Events page, you can use the Search filter to find the events to be delivered as alerts. You can filter the events by Event Name and Severity. Once you select the events, select the Show Selected toggle button to preview the selected events, and select +Add To Alerts.

   The selected events will be configured as Alerts, using the existing configured Alert Notification method, and will appear under the Events area of the Alert Configuration screen.

   

4. Select Save Changes.

   In the Events page, select an event and select Remove to remove the event from the Events list. To add new custom events to the existing Events list, contact your Operator User.