Risks, Limitations and Assumptions

  • AThe application handles Critical/Recovery failure notifications for the following two cases when user enables App Failure Notifications in configuration.
    • Connectivity Exception
    • Authentication Exception
  • The app sends duplicate or repeat failure alert notifications every 6 hours.
  • Metrics help monitor RabbitMQ resources and generate alerts based on threshold values.
  • You can set the RabbitMQ using an IP address or hostname with a port. Hostname works only if name resolution is available.
  • This app supports only Classic Gateway and NextGen Gateway.
  • Cluster Gateway is not supported.
  • Activity log and applied time are not displayed.
  • You can configure component-level thresholds for each resource.
  • Latest snapshot metric support is available from Gateway version 14.0.0.

Troubleshooting and FAQs

  • Ensure to follow all the prerequisites mentioned in Prerequisites are met.

  • When RabbitMQ integration fails to Discover / Monitor, follow these troubleshooting steps.

    • Check if any alerts generated on RabbitMQ System resource or on the gateway or any error logs in vprobe.
    • To rule out API accessibility or specific failures like end device connectivity or authentication, try to check the reachability of end device from gateway using following commands
      • Try ping with IP Address provided in configuration
        ping <IP Address>
      • Try telnet using telnet
        telnet
      • If still need assistance, reach out to Support Team to check DB / SSH accessibility using SDK App Debug Command Center (depends on gateway version 18.1.0 and app support) OR DiscoveryandMonitoring-TargetAPIResponses.

  • If there is no connectivity or authentication issues, see SDK App Debugging process and reach out to Support Team for further assistance.