Risks, Limitations & Assumptions

• App can handle Critical/Recovery failure notifications for the following two cases when user enables “App Failure Notifications” in configuration
  • Connectivity Exception
  • Authentication Exception
• App will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
• App does not control monitoring pause/resume actions based on above alerts.
• This app supports only Classic GW and NextGen Gateway. Not supported with Cluster GW.
• The Template Applied Time is displayed only if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
• Add Each subscriber or publisher must be added as a separate configuration in this integration.
• As observed in the CUCM clusters, duplicate devices may exist across subscribers until the cluster is cleaned up. Example: When a user unregisters from subscriber1 and registers to subscriber2, the device will be deleted from subscriber1, causing its monitoring data to be lost. Then, a new device will be discovered under subscriber2. Additionally, if the user does not clean up the unregistered phones on subscriber1, alerts will be generated until the end device cleanup occurs.
• During this period, alerts may be triggered based on the configured thresholds. Please note that device counts might not exactly match between OpsRamp and the target devices.