A Hyper-V host may trigger VMware-specific alerts if Auvik classifies the device as a VMware hypervisor. This can occur when the device reports a VMware-like identifier, such as a VMware-related system description or software build string.
Symptoms
- A Hyper-V host appears as a VMware hypervisor in Auvik.
- VMware-specific alerts are generated for the host.
- VMware credentials or VMware component monitoring appear to be associated with the device.
Why this happens
Auvik uses information reported by the device and discovered services to classify the platform. If a Hyper-V host or its management layer reports a VMware-like identifier, Auvik may apply VMware monitoring logic to the device.
Exclude the Hyper-V host from VMware alerts
If the device is correctly identified as a Hyper-V host outside Auvik, exclude it from the VMware alert definitions that are generating incorrect notifications.
- Go to Manage Alerts.
- Open the Alerts 2.0 table.
- Locate the VMware alert definition that is generating the notification.
- Select the alert and click Edit.
- In the entity scope, exclude the affected Hyper-V host.
- Save the alert definition.
- Repeat these steps for any other VMware-specific alerts affecting the host.
If the VMware alerts are not required for the site, you can disable them at the appropriate site or alert scope. Avoid disabling a shared alert definition if other VMware hosts still require monitoring.
Correct the device identification
If the host is reporting an incorrect VMware-like identifier, have the Hyper-V or management-platform administrator verify and correct the reported system information.
After the information is corrected:
- Confirm that the host is reachable by the Auvik collector.
- Allow a successful poll or discovery cycle to complete.
- Review the device classification in Auvik.
- Confirm that the host is no longer being treated as a VMware hypervisor.
Changes to the host’s system description, software build, or management-platform reporting are made outside Auvik.
Verify the resolution
After updating the alert scope or correcting the device identification:
- Confirm that the Hyper-V host is excluded from VMware alert entities, or that Auvik now classifies it correctly.
- Confirm that VMware credentials or VMware monitoring are not being applied incorrectly.
- Monitor the host for new VMware notifications.
- Verify that legitimate VMware hosts continue to generate the alerts they require.
If the problem continues
Contact Auvik Support if the host remains misclassified after a successful poll or discovery cycle.
Include:
- Host manufacturer and model.
- Hyper-V version.
- Reported system description or software build.
- Auvik device classification.
- VMware alert names and timestamps.
- Screenshots showing the incorrect classification.
- Any VMware credentials or services incorrectly associated with the host.