Notifications

Notifications provide a way to notify you when an alert condition is triggered within APM. You can be notified by Email or via SNMP. You can also have APM send events to a server or servers for processing.

Email notifications

Email notifications provide a way to notify you by email when events (triggered by alert threshold violations/clears) occur on your network. A notification can be sent immediately when an event occurs, it can be delayed and sent only if the event persists for a period of time, or it can be collected with other events in a “Digest summary” and sent at intervals ranging from every five minutes to once a day.

The set of rules that determine when notifications are generated and sent are called notification profiles. Custom notification profiles provide you flexibility in notifying selected recipients when specific events in specific organizations occur. Within a profile you can specify the organization, the paths, the events that trigger notifications, the email addresses to which notifications are sent, and the frequency of the notifications. Any events that are not handled by a custom notification profile are handled by the “Default” profile.

A list of default email addresses is provided and is applied to each profile by default. This list can be overridden by creating a per-profile email address list.

In addition to being notified when network events occur, you can be notified when system service/maintenance events are scheduled.

View a profile

  1. Navigate to > Update Notification Options.
  2. For the profile you want to view, click to the left of the profile name. The profile configuration is listed.

The default profile

The “Default” profile is used to notify on events not handled by a custom profile. It encompasses all organizations and all network paths, includes the default list of email recipients, and provides the default configuration for each of the event types. You can edit the default profile just like a custom profile.

Create a custom profile

  1. Navigate to > Update Notification Options.
  2. Click + Add Profile.
  3. In the Name field, enter the name of the profile.
  4. In the Organization dropdown, select the organization associated with the profile.
  5. Click Submit. The profile is created. You still need to edit it in order to activate it.

Edit a profile

  1. Navigate to > Update Notification Options.
  2. For the profile you want to edit, click to the left of the profile name. The profile configuration is listed.
  3. Select the checkboxes for all event types you want to receive notification emails for.
  4. For each event type selected, specify the notification profile configuration.
  5. If you are using a Digest summary notification type, set the Digest Period.
  6. Click Save. The profile configuration is updated.
  7. Click to the left of the profile name to collapse the configuration.

Note: If different Digest Periods are needed for different event types, then separate notification profiles are required.

Notification profile configuration

A custom notification profile looks as follows:

Screen shot of the notification profile configuration screen.

Event types

Event Type Definition
Network path alert profile Violate/Clear events Network path events occur when Delivery alerts are triggered.
Web path alert profile Violate/Clear events Web path events occur when Experience alerts are triggered.
Network route change events Network route change events occur when there is a change to the sequence of Autonomous System (AS) numbers from the path source to its target (indicating a change in provider network). These events are system defined so are not required in an alert profile to trigger, but notifications for the events can be enabled or disabled.
Flow analysis alert profile Violate/Clear events Flow analysis events occur when Usage alerts are triggered.
Monitoring Point Availability event Monitoring Point availability events occur when a Monitoring Point disconnects or reconnects to APM.

Notification types

Notification type Definition
Immediate A notification email is sent when each violation/clear event occurs.
Violation persists for A notification email is sent if a violation persists for a specified period of time.
Digest summary A notification email is sent at the end of each Digest Period. The email contains a Digest Summary - a collection of all events of a given type that occurred during the Digest Period.

Notify about network path events

Network path events occur when Delivery alerts are triggered. To trigger email notifications:

  1. Select the checkbox for Network path alert profile Violate/Clear events.
    • By default, a Digest Summary is generated for alerts on all network paths.
  2. (Recommended) To notify about a subset of paths rather than all paths:
    1. Click to remove the default (All Network Paths) configuration.
    2. Click Add List….
    3. Select a Saved List containing the network paths you want to notify on.
    4. Select the notification type (Immediate, Violation persists for, or Digest summary).
    5. Click Add. The configuration for the selected Saved List is added.
  3. (Optional) Repeat for additional Saved Lists.
  4. If you are using a Digest summary, set the Digest Period.
    • Note that the Digest Period applies to all event types within the profile.
  5. Click Save.

Note: You can also choose to receive additional notices when a diagnostic test completes and/or fails.

Notify about web path events

Web path events occur when Experience alerts are triggered. To trigger email notifications:

  1. Select the checkbox for Web path alert profile Violate/Clear events.
    • By default, a Digest Summary is generated for alerts on all web paths.
  2. (Recommended) To notify about a subset of paths rather than all paths:
    1. Click to remove the default (All Network Paths) configuration.
    2. Click Add List….
    3. Select a Saved List containing the web app groups you want to notify on.
    4. Select the notification type (Immediate, Violation persists for, or Digest summary).
    5. Click Add. The configuration for the selected Saved List is added.
  3. (Optional) Repeat for additional Saved Lists.
  4. If you are using a Digest summary, set the Digest Period.
    • Note that the Digest Period applies to all event types within the profile.
  5. Click Save.

Notify about network route change events

Network route change events occur when there is a change to the sequence of Autonomous System (AS) numbers from the path source to its target (indicating a change in provider network). These events are system defined so are not required in an alert profile to trigger, but notifications for the events can be enabled or disabled.

To avoid receiving excessive network route change notifications, we recommend enabling this feature only in cases where network route changes are unexpected.

Note that network route change events are different from the Route change alert profile condition.

To trigger email notifications:

  1. Select the checkbox for Network route change events.
    • By default, a Digest Summary is generated for alerts on all network paths.
  2. (Recommended) To notify about a subset of paths rather than all paths:
    1. Click to remove the default (All Network Paths) configuration.
    2. Click Add List….
    3. Select a Saved List containing the network paths you want to notify on.
    4. Select the notification type (Immediate or Digest summary).
    5. Select the protocols you want to notify on (ICMP, UDP, and TCP).
    6. Click Add. The configuration for the selected Saved List is added.
  3. (Optional) Repeat for additional Saved Lists.
  4. If you are using a Digest summary, set the Digest Period.
    • Note that the Digest Period applies to all event types within the profile.
  5. Click Save.

Notify about flow analysis events

Flow analysis events occur when Usage alerts are triggered. To trigger email notifications:

  1. Select the checkbox for Flow analysis alert profile Violate/Clear events.
    • Note that there is no Flow analysis alert profile applied to all Monitoring Points by default.
  2. Select the notification type (Immediate, Violation persists for, or Digest summary).
  3. If you are using a Digest summary, set the Digest Period.
    • Note that the Digest Period applies to all event types within the profile.
  4. Click Save.

Notify about Monitoring Point availability events

Monitoring Point availability events occur when a Monitoring Point disconnects or reconnects to APM. To trigger email notifications:

  1. Select the checkbox for Monitoring Point Availability event.
  2. Select the notification type (Immediate, Violation persists for, or Digest summary).
  3. If you are using Immediate or Violation persists for you can specify the time range for notifications.
  4. If you are using a Digest summary, set the Digest Period.
    • Note that the Digest Period applies to all event types within the profile.
  5. Click Save.

Tip: Using a “Violation persists for” notification type of 10 to 15 minutes allows a Monitoring Point to disconnect from APM for a short time without generating an alert notification. If it is able to continue monitoring and is reconnected within this period, monitoring data is uploaded to APM as normal.

Rename a profile

  1. Navigate to > Update Notification Options.
  2. For the profile you want to rename, select > Rename Profile.
    • Note that the “Default” profile cannot be renamed.
  3. In the New Name field, enter the new name for the profile.
  4. Click Submit. The profile is renamed.

Delete a profile

  1. Navigate to > Update Notification Options.
  2. For the profile you want to delete, select > Delete Profile.
    • Note that the “Default” profile cannot be deleted.
  3. Click OK. The profile is deleted.

Edit per-profile email addresses

By default, all profiles use the default email address list. You can override this by creating a separate list of email addresses for the profile.

  1. Navigate to > Update Notification Options.
  2. For the profile you want to edit, select > Edit Email Addresses.
  3. Select Override Default Email Addresses.
  4. In the To field, enter the email address of the primary recipient.
  5. In the Cc field, enter the email addresses of additional recipients.
  6. Click Submit. The email addresses associated with the profile are updated.

Edit default email addresses

  1. Navigate to > Update Notification Options.
  2. Click the link next to the Default Email Addresses field.
  3. In the Notification Email field, enter the email address of the primary recipient.
  4. In the Cc Addresses field, enter the email addresses of additional recipients.
  5. Click Submit. The default email addresses are updated.

Enable/Disable Service Bulletins

Service bulletins are emails notifying you of system upgrades, scheduled maintenance, and other important information about the AppNeta Performance Manager service. Service Bulletins, when enabled, are sent to the email addresses on the default email address list.

  1. Navigate to > Update Notification Options.
  2. To enable Service Bulletins, select Yes in the Enable Service Bulletins field.
  3. To disable Service Bulletins, select No in the Enable Service Bulletins field.

SNMP notifications

You can configure APM to generate SNMP notifications (traps/informs) upon Delivery and Experience monitoring violation and clear events for all paths in an organization as well as when a Monitoring Point is created and when it goes either offline or online. SNMP notifications are not available for Usage monitoring events.

You must designate one or two Monitoring Points to send the SNMP notifications generated by APM to your SNMP NMS or NMSs (up to eight NMSs can be specified). All messages are sent by the designated senders to all configured NMSs. You also need to load the AppNeta MIB on all specified NMSs.

Configure SNMP notification forwarding

Organization Admin privileges are required to configure this feature.

  1. Navigate to > Manage SNMP.
    • If you do not see the Manage SNMP option, you do not have the necessary (Organization Admin) privileges.
  2. Configure a Primary sender and optionally a Secondary sender.
    • Note that the NMS Hosts field can contain multiple NMS IP addresses or hostnames.
  3. Click Test SNMP Traps to test your configuration.
  4. Click Apply. SNMP notification forwarding is configured.

Load AppNeta MIB on NMSs

  1. Navigate to > Manage SNMP.
    • If you do not see the Manage SNMP option, you do not have the necessary (Organization Admin) privileges.
  2. Click the download the latest MIB link to download the AppNeta MIB to your computer.
  3. Copy the MIB to each NMS that will receive AppNeta notifications.