Smart Notifications

Traverse correlates OK notifications with prior non-OK notifications. So if you first receive an email for critical state, you also get a notification when the test returns to OK state. However, if your action profile is set up in such a way that the test returns from critical to OK state before notification for critical state is sent (e.g. wait 2 test cycles), notification for OK state is not sent either. If you want to disable this behavior (i.e. be notified of OK state regardless), you can disable the Smart Notification option for the device in question via Administration > Devices > Update.

Traverse's Smart Notification was designed to eliminate sending multiple notifications when a device goes down or is unavailable. Often, many configured tests on a device have action profiles assigned to them to notify various recipients when test status reaches Warning, Critical, Unknown, or all three.

Smart Notification relies on the inherent dependency between the ping packet loss test results and the availability of the device. If the ping packet loss test returns 100%, then communication with the device has somehow been lost. This could result in all tests sending notifications every test cycle, especially if they are configured to notify on Unknown, which is what the test results will likely be in this situation.

Configuring Smart Notification During New Device Configuration

1. Navigate to Administration > Devices.
2. Click the Create A Device link. For a detailed description of device creation, see Managing Tests.
3. Fill out the required information in the Create Device page.
4. Check the box labeled Smart Notification.
5. Click Create Device to begin test discovery.

If you are receiving notifications when the device is down you should check the following items:

• Confirm that you have in fact configured Smart Notification on the device by navigating to the Manage Devices page and selecting the Update link for the device. The Smart Notification box should be checked.
• Confirm that you have a Packet Loss test configured on the device by navigating to the Manage Devices page and selecting the Tests link for the device. The list of test should include the Packet Loss test.
• If both of the above are configured properly, the notifications that you have received are likely a result of having been queued up prior the Packet Loss returning 100%. That is, if tests are scheduled in the queue ahead of the Packet Loss test, they will be executed prior to the trigger that suppresses all further notifications when Packet Loss = 100%.

To avoid notifications in this case it is advisable that you change your action profiles to either:

• Not notify on UNKNOWN; or
• Only notify after 2 or 3 test cycles have passed.