Risks, Limitations & Assumptions

  • The integration can manage critical/recovery failure alerts for the following two scenarios when the user activates App Failure Notifications in the settings:
    • Connectivity Exception
    • Authentication Exception
  • VMWare vRealize Orchestrator will send any duplicate/repeat failure alert notification for every 6 hours.
  • VMWare vRealize Orchestrator cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor PowerMax resources and can generate alerts based on the threshold values.
  • We have provided 22 as default SSH Port value for connecting to VRO end device via SSH. Users can modify this value from the application configuration page at any point of time if required.
  • Mention the ports that need to be monitored in Ports to be monitored. By default we are providing 22, 443, 5480, 80,8281, 8283 ports in this field.
  • Component level thresholds can be configured on each resource level.
  • No support of showing activity logs.
  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
  • Latest snapshot metric support from gateway 14.0.0.
  • For metrics vmware_vrealize_orchestrator_port_Status and vmware_vrealize_orchestrator_url_Status, we are sending status as CLOSE and CRITICAL respectively in case of any failures like connection issues etc.,