Network Management

IP SLA Operation Canned Alert with custom property

This article describes the issue with the custom property that cannot be applied to an alert.

First published date

10/19/2018 9:30 PM

Last published date

10/19/2018 9:30 PM

Overview

This article describes the issue with the custom property that cannot be applied to an alert.

 

Product section

VoIP & Network Quality Manager

Cause

This issue occurs when the custom property may not have been committed to database before being assigned to alert.

Resolution

  1. Edit the alert. 
  2. In the IP SLA Operation Alert, remove and re-add the filter for the custom property.
  3. Leave the default triggger actions alone for Node Status is not down or not unmanaged.
  4. Leave the default trigger action alone for Operation status is not equal to warning and critical.

Note: If you have an additional trigger condition for a custom property, remove it, and then add it again. Submit the changes and test if everything is working fine.