Risks, Limitations and Assumptions
Azure Arc can manage critical and recovery failure notifications for the following two cases when the user enables App Failure Notifications in the configuration settings:
- Connectivity Exception
- Authentication Exception
The integration will send duplicate or repeated failure alert notifications every 6 hours.
Note: The integration does not control monitoring pause or resume actions based on these alerts. Metrics can be used to monitor resources and generate alerts based on threshold values.
- OpsRamp provides port 443 as the default value for processing APIs. Users can modify this value on the application configuration page if needed.
- Activity logs and applied time are not supported for display.
- The minimum supported version to access the latest snapshot metric option is nextgen-14.0.0.
- Full discovery support requires gateway version 15.0.0 or above.
- The integration is not compatible with the Cluster Gateway.
- Monitoring frequency should not be set to less than 5 minutes, as Insight metrics APIs provide incorrect data with 5-minute polling intervals.
Troubleshooting
- Ensure all the prerequisites mentioned are met
- When Azure Arc integration fails to Discover / Monitor, please complete the following troubleshooting steps
- Check if any alerts generated on Azure Tenant or on the gateway or any error logs in vprobe.
- If the error/alert is related to End Device Connectivity or Authentication issue, try to check reachability of end device from gateway using following commands:
- try ping with IP Address provided in configuration
ping <IP Address>
- try telnet using telnet
<IP Address> <port>
- try ping with IP Address provided in configuration
- If further assistance is needed, please reach out to the support team to check API accessibility using the internal API commands utilized on the app side.