Risks, Limitations and Assumptions

  • Application can handle Critical/Recovery failure alert notifications for following two cases when user enables** App Failure Notifications** in configuration.
    • Connectivity Exception
    • Authentication Exception
  • Application will send any duplicate/repeat failure alert notification for every six hours.
  • Application cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor HPE Serviceguard resources and can generate alerts based on the threshold values.
  • HPE Serviceguard Event/Alert polling will be started only if the user enables Event Polling in configuration. Possible values of Alert Severity Filter configuration are “DEGRADED”,“WARNING”,“CRITICAL”,“ERROR”. Based on these values alerts will be filtered and user can customize this at any point of time.
  • OpsRamp has given default mappings to map Serviceguard alerts Severity with OpsRamp Severities as part of Alert Severity Mapping configuration. User can modify them as per their use-case at any point of time from application configuration page. Possible OpsRamp Severities are Critical, Warning. Provided below default severity mapping in configuration{“DEGRADED”:“Critical”,“WARNING”:“Warning”,“CRITICAL”:“Critical”,“ERROR”:“Warning”}
  • In Alert polling, by default alert will be raised on root resource. User can make the alert populated on its actual resource by unchecking the checkbox(Alert on root Resource).
  • OpsRamp has provided** 5522** and **22** as default Port for API and SSH respectively. Users can modify this value from configuration page if requires.
  • Component level thresholds can be configured on each resource level.
  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
  • The minimum supported version for the option to get the latest snapshot metric and Full discovery is Nextgen-15.0.0.
  • This application supports both Classic Gateway and NextGen Gateway.