Verify the Metrics Collected by Aria Operations from vCenter
- Log in to the vSphere console and browse to the VM
- Click on the Monitor > Advanced tab
- Click Chart Options
- In the Chart Metrics: click Network and place a check in the box for the Counter named Transmit packets dropped
- Review the chart at the same time frame that the alert was triggered in Aria Operations
Note: vCenter creates data points every 20 seconds for the Real-time graph. Aria Operations collects data from the vCenter every 5 minutes (by default). This results in a data point in Operations that represents the sum of 15 of the 20 second vCenter data points.
Workaround 1 - Increase the Alert Wait Cycles
Increasing the Wait Cycle for the alert will cause the alert to be less sensitive to transient events. The alert will not trigger unless the dropped transmit packets are occurring above the threshold for a consecutive number of collection cycles.
- Log in to the Aria Operations UI and browse to Operations > Configurations > Alert Definitions
- Type
VM network has dropped transmit packets in the filter in the top right and press Enter
- Click the vertical 3 dot button and select Edit
- In the 1 - Alert tab, expand Advanced Settings
- Change the Wait Cycle to 3 and click Update
Alert Definition Best Practices - Wait and Cancel Cycle
Creating Alert Definitions - Wait Cycle
Workaround 2 - Increase the Alert Threshold
The alert threshold values of 10 and 20 dropped packets are suggested values that may not be appropriate for your environment. Use the steps below to update the alert thresholds with your desired values.
- Log in to the Aria Operations UI and browse to the VM that raised the alert
- Click the Policy dropdown menu and click View Policy
- Click Edit Policy
- Click the Alerts and Symptoms tile
- Type
VM network has dropped transmit packets in the filter in the top right and press Enter
- Select the VM network has dropped transmit packets alert definition to reveal the settings
- Modify the values for the Immediate and Critical level as appropriate for your environment
- Click Save
- Repeat steps 1-8 for any remaining policies in the environment that should be modified
Note: The recommended values >20 for Immediate level and >10 for Critical level are reversed. This will be fixed in an upcoming version of the product. The steps in Workaround 2 can be used to correct the values to the intended values of >10 for Immediate level and >20 for Critical.