This is the expected behavior. You can disable alerts for hosts in maintenance by using a custom group and policy. Create a custom group with the membership criteria set to include only hosts in maintenance:
Create a new policy off your default policy and disable all of the host alerts. Assign this policy to the group for hosts in maintenance. This should disable any host alerts while the host is in maintenance and move the host back to your default policy when it exits maintenance.
Putting the host object in vROps in maintenance mode will also stop the alerts, but I don't think it's as simple to automate. Alan has some nice functions in PowerCLI.
You'd have to call this from vCenter or vRO when the hosts enter and exit maintenance mode.
I did this the opposite way but both would work
I created several groups ( Production ESXi hosts, Non production ESXi Host) and so on And my group membership rules include a statement that the host must not be in maintenance mode. When we put a host into maintenance mode they drop out of the different policies assigned to the different groups into the default policy that does not alert.
Either way will work depending on how you use policies. My way works for me as i have 4 different policies for different environments that have different capacity thresholds and alerting. If you have one policy (default) then dtaliafe reply works great as you only need to create a sub policy off the default and assign to one group
Today, when vCenter places a host in maintenance mode, there is no connection to tell vROps that the host should be in maintenance mode there too. To showcase the versatility of vROps, here is yet another approach to maintenance mode.
This blog explains two ways for utilizing maintence mode:
- Manually put a resource, like a host, in vROps maintenance mode and then take it back out. If you have many hosts going into maintenance mode at a time, the previously mentioned options might work better.
- Using schedules, hosts can automatically enter and exit vROPs maintenance mode on a set schedule without interaction required.
This solution, although appealing, it's not really useful to us because it only refreshes the hosts inside the custom group every 20 mins. So, by the time, vRops puts my host in this custom group, the maintenance will be probably over, or underway, and the alarms are already being notified to other team members.