Risks, Limitations and Assumptions

  • The integration can handle Critical/Recovery failure notifications for the following two cases when user enables App Failure Notifications in configuration
    • Connectivity Exception
    • Authentication Exception
  • The integration will send any duplicate/repeat failure alert notification for every 6 hours.
  • The integration cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor resources and can generate alerts based on the threshold values.
  • The minimum supported version for the option to get the latest snapshot metric is nextgen-14.0.0.
  • Full discovery support requires gateway version 15.0.0 or above.
  • The integration is not compatible with Cluster Gateway

Troubleshooting

  • Ensure all the prerequisites mentioned are met.
  • When the Microsoft SCVMM integration fails to discover or monitor, perform the following troubleshooting steps:
    • Check if any alerts are generated on the cluster, gateway, or any error logs in vprobe.
    • To rule out PowerShell connection issues or failures like end device connectivity or authentication, establish a connection with the end device from the gateway using the following steps:
      • For NextGen Gateway, use the command:
        kubectl exec -it nextgen-gw-0 -c nativebridge -- /bin/bash
        to connect to the native bridge container. Once connected, proceed to run the following commands.
      • For Classic Gateway, directly run the following commands:
      • Launch PowerShell using:
        pwsh
      • Run the following commands to establish connection. Replace <password>, <username>, and <ipAddress> with actual values before executing the commands:
        • 
$pw = ConvertTo-SecureString -AsPlainText -Force -String "<password>"
$cred = new-object -typename System.Management.Automation.PSCredential -argumentlist "<username>", $pw
$session = new-pssession -computername "<ipAddress>" -credential $cred -Authentication Negotiate -ErrorAction Stop
$session.state
      • If the session is established, ensure all prerequisites are met.
    • If connectivity or authentication issues persist, refer to the SDK App Debugging process and contact the Support Team.