Alerts and Notifications

Generate Alert Notifications

• Configure a Notification Profile

• Enable Alert Notifications for a Device Group or Network Group

Configure a Notification Profile

A notification profile defines the delivery method to use for sending notifications.

1. Click the Settings > System option in the left-nav bar.
2. Click the Notification tab on the left of the window. click the add notification button (+ Notification).
3. Click the + Notification button
4. In the Add Notification window that appears, configure the notification profile:

   Attributes	Description
   Name	Enter a name.
   Description	(Optional) Enter a description.
   Notification Type	Select a notification type: Web Hook Slack Kafka Publish Microsoft Teams (HealthBot 2.1.0 and later) EMails (HealthBot 2.1.0 and later) Advanced Message Queuing Protocol (AMQP) Publish (Paragon Insights Release 4.0.0 and later) Notification type attributes vary based on notification type selected. See below for details.

5. Click Save and Deploy.

NOTIFICATION TYPE DETAILS

Web Hook

• URL—URL at which the Web Hook notification should be posted.
• Username—(Optional) Username for basic HTTP authentication.

• Password—(Optional) Password for basic HTTP authentication.

Slack

• URL—URL at which the Slack notification should be posted. Different from your Slack workspace URL. Go to https://slack.com/services/new/incoming-webhook and sign in to your Slack workspace to create a Slack API endpoint URL.

• Channel—Channel on which the notification should be posted.

Kafka Publish

• Bootstrap Servers—Add Kafka host:port pairs from the drop-down list to establish the initial connection to the Kafka cluster.
• Topic—(Optional) Name of the Kafka topic to which data will be published. By default, the Kafka topic naming convention for device group alert notifications is device-group.device-id.topic.rule.trigger.

Depending on the authentication protocols being used, the required authentication parameters are as follows:

• Username—Username for SASL/SSL or SASL/plaintext authentication.
• Password—Password for SASL/SSL or SASL/plaintext authentication.
• Certificate—Kafka server’s CA certificate. Choose file from the drop-down list.
• Upload Certificate—Location from where the Kafka server’s CA certificate will be uploaded. Click Choose files and navigate to the file location. File should be in Privacy Enhanced Mail (PEM) format.

Microsoft Teams

As of HealthBot Release 2.1.0, you can send Paragon Insights (formerly HealthBot) notifications to Microsoft Teams. Teams can provide a connector which you can add to Paragon Insights to enable the connection.

• In Teams, create a new connector set as an incoming webhook.

• Copy the URL provided by Teams.

• In Paragon Insights, configure a notification profile that sends to Microsoft Teams.

• Apply the notification profile to a device group.

1. In Teams, select the desired channel and click the ellipsis (...).
2. In the menu that appears, click Connectors.

   

3. Use the Incoming Webhook option and click Configure.

   

4. On the next page, click Create.

   

5. Once the web hook is successfully created, copy the provided URL.

   

6. In Paragon Insights, go to the Settings > System page select the Notification tab.
7. Click the + Notification button.
8. Configure the notification profile as follows:

   • Name - Enter a profile name.

   • Notification Type - select Microsoft Teams.

   • Channel - Paste the URL provided by the Teams UI above.

9. Click Save and Deploy.
10. Apply the notification profile to a device group or network group as shown in Enable Alert Notifications for a Device Group or Network Group

EMails

As of HealthBot Release 2.1.0, you can send Paragon Insights (formerly HealthBot) notifications by email. By default, email notifications cover all running playbooks and rules for the device group or network group to which they are applied, however you can narrow the focus by selecting specific rules.

• In Paragon Insights, configure a notification profile that sends to email.

• Apply the notification profile to a device group.

1. In Paragon Insights, go to the Settings > System page.
2. Select the Notification tab and click the the + Notification button.
3. Configure the notification profile as follows:

   • Name - Enter a profile name.

   • Notification Type - Select Emails.

   • Email Addresses - Enter an email address and click Add <email-address>; repeat for more email addresses.

   • (Optional) Rule filters - To narrow the scope of what triggers an email, define rule filters. Enter a filter and click Add <rule-filters>; repeat for more filters.

     • Format is topic/rule; can use regular expressions

     • Example: interface.statistics/check-interface-flaps sends notifications only for the rule check-interface-flaps.

     • Example: system.processes/.* , system.cpu/.* , and interface.statistics/.* sends notifications for all rules under the topics system.processes, system.cpu, and interface.statistics.

4. Click Save and Deploy.
5. Apply the notification profile to a device group or network group as shown in Enable Alert Notifications for a Device Group or Network Group

AMQP Publish

• Host (mandatory)—Specify a valid hostname or the IP address of the AMQP server.

• Port (mandatory)—Specify the listener port of the AMQP server.

• Exchange(mandatory)—Specify the name of the exchange or the routing agent of the AMQP server on which the connection must be instantiated.

• Virtual Host(optional)—Specify the virtual host of the AMQP server on which the connection must be instantiated. If you do not specify, the default value(/) is used.

• Routing Key(optional)—Specify the routing key. The routing key is a message attribute that the exchange refers to when deciding how to route the message to the queue.

  Note

  If you have not configured the routing key, the following are the default value:

  • For sensor or raw data, <device-group>.<device>.sensors

  • For field data, <device/network-group>.<device>.<topic>.<rule>.fields

  • For trigger/alert data, <device/network-group>.<device>.<topic>.<rule>.<trigger>

  In case of a network group, <device> is rendered as “-”.

• Username—Specify the username for the Simple Authentication Security Layer (SASL) authentication.

• Password—Specify the password for the SASL authentication.

• CA Profile—Select the CA profile from the drop-down list. For more information on CA Profiles and local certificates, see Configure a Secure Data Connection for Paragon Insights Devices.

• Local Certificate—Select the local certificate from the drop-down list. For more information on CA Profiles and local certificates, see Configure a Secure Data Connection for Paragon Insights Devices

• Server Common Name—Specify the server common name that is used while creating a certificate.

Enable Alert Notifications for a Device Group or Network Group

To enable alert notifications for a device group or network group:

1. For Device Groups, select the Configuration > Device Group page from the left-nav bar.

   For Network Groups, select the Configuration > Network page from the left-nav bar.

2. Click the name of the device group or network group for which you want to enable alert notifications.
3. Click the Edit (Pencil) icon.
4. Scroll down to the Notification section in the pop-up window and click the caret to expand that section.
5. Select a destination for any alert level (Major, Minor, or Normal) that you want. Notification can be sent to zero or more defined destinations for each alert level.
6. Click Save and Deploy.

Manage Alerts Using Alert Manager

• Viewing Alerts

• Manage Individual Alerts

• Configure Alert Blackouts

Viewing Alerts

To view the alerts report table, go to the Monitor > Alerts page in the left-nav bar. Note that Alert Manager consolidates duplicate alerts into one table entry and provides a count of the number of duplicate alerts it has received.

Starting with release 4.2.0, Paragon Insights generates smart alerts if you configured resources and dependencies. To configure resources, click Resource Discovery at the top right corner of the Alerts page.

Smart alerts combine alerts from different rules into a collapsible tree structure. The main alert in the tree displays the root cause that triggered the other alerts in the tree. See Understand Resources and Dependencies for more information.

The following table describes the alerts report table attributes.

The following table describes the main features of the alerts report table:

Manage Individual Alerts

You can view detailed information about each alert in the alerts report table. You can also assign a management status (such as open, ack, and close), and apply simple actions (such as shelve and delete) to each alert.

To manage individual alerts:

1. Go to the Monitor > Alerts page from the left-nav bar to open the alert report table.

2. Click on a single alert entry in the table. The Alert Details pane displays detailed information about the alert.

The following table describes the set of buttons at the top of the Alert Details pane:

Configure Alert Blackouts

You can configure blackout periods to suppress or mute alerts during, for example, scheduled downtimes.

To configure blackouts:

1. Click the Settings > System page from the left-nav bar.

2. Select the Alert tab on the left side of the page.

3. In Alert Blackout Settings, click the + Alert Blackout button.

4. Enter the necessary values in the text boxes for the blackout configuration.

   The following table describes the attributes in the Add an Alert Blackout pane:

   Attributes	Description
   Duration	Select a start and end date and time for the blackout.
   Device Group	Select a device group from the drop-down list to which to apply the blackout configuration.
   Attribute	(Optional) Specify an attribute from the drop-down list to which to apply the blackout configuration.
   Value	(Optional) If a blackout attribute is specified, provide an associated value (as shown in the alerts report table). Only the alerts that match this attribute value exactly will be suppressed from the alerts report table. Note: For the Resource-Event attribute, you must specify a resource from the drop-down list, as well as specify an Event value. Only the alerts generated by the specified resource that match this Event value exactly will be suppressed from the alerts report table.

5. Click Save to save the configuration.

6. (Optional) Click the Delete button to delete a blackout configuration.

Stream Sensor and Field Data from Paragon Insights

• Configure the Notification Type for Publishing

• Publish Data for a Device Group or Network Group

Configure the Notification Type for Publishing

Paragon Insights supports Apache Kafka and AMQP for publishing sensor and field data.

You must first configure a Kafka publishing profile before you can start publishing sensor and field data for a specific device group or network group.

To configure a Kafka publishing profile:

1. Select the Settings > System page from the left-nav bar.
2. Click the Notification tab on the left part of the page.
3. In Notification Settings, click the + Notification button.
4. Enter the necessary values in the text boxes and select the appropriate options for the Kafka publishing profile.

   The following table describes the relevant attributes in the Add a Notification Setting and Edit Notification Configuration panes:

   Attributes	Description
   Name	Name of the notification.
   Description	(Optional) Description of the notification.
   Notification Type	Click the Kafka publish radio button.
   Kafka Publish	Bootstrap Servers—Add Kafka host:port pairs from the drop-down list to establish the initial connection to the Kafka cluster. Topic—(Optional) Name of the Kafka topic to which data will be published. By default, the Kafka topic naming conventions are: For device group field data, device-group.device-id.topic.rule.fields For network group field data, network-group.topic.rule.fields o For device group sensor data, device-group.device-id.sensors Depending on the authentication protocols being used, the required authentication parameters are as follows: SASL/SSL—Username, password and certificate SASL/Plaintext—Username and password SSL—Certificate Plaintext—None Required authentication parameters are: Username—Username for SASL/SSL or SASL/plaintext authentication. Password—Password for SASL/SSL or SASL/plaintext authentication. Certificate—Kafka server’s CA certificate. Choose file from the drop-down list. Upload Certificate—Location from where the Kafka server’s CA certificate will be uploaded. Click Choose files and navigate to the file location. File should be in Privacy Enhanced Mail (PEM) format.

5. Click Save to save the configuration or click Save and Deploy to save and deploy the configuration.
6. Apply the Kafka publishing profile to a device group or network group. For more details, see the Publish Data for a Device Group or Network Group section.

Publish Data for a Device Group or Network Group

To publish Paragon Insights sensor or field data for a device group or network group:

1. For Device Groups, select the Configuration > Device Group page from the left-nav bar.

   For Network Groups, select the Configuration > Network page from the left-nav bar.

2. Click the name of the device group or the network group to which you want to publish data.
3. Click the Edit (Pencil) icon.
4. Under Publish, select the appropriate Destinations, Field, or Sensor from the drop-down lists for the data you want to publish. To publish field or sensor data, you must configure a destination.

   Parameter	Description
   Destinations	Select the publishing profiles that define the notification type requirements (such as authentication parameters) for publishing the data. To edit or view details about saved publishing profiles, go to the System page under the Settings menu option in the left-nav bar. The publishing profiles are listed under Notification Settings. Note: Only Kafka and AMQP publishing are currently supported.
   Field	Select the Paragon Insights rule topic and rule name pairs that contain the field data you want to publish.
   Sensor	(Device group only) Select the sensor paths or YAML tables that contain the sensor data you want to publish. No sensor data is published by default.

5. Click Save to save the configuration or click Save and Deploy to save and deploy the configuration.