Custom disk alerts in a cluster is lost when instance is moved to a new host
We often use customized disk alerts for larger disks i.e. instead of using the default alerts we might configure a High alert at 200 GB and a medium at 250 GB.
These custom alerts is not set on the instance level so when we move the instance to a new host the custom alerts will not follow the instance and the alert has to be set up again.
As our largest cluster is 9 node cluster with 23 instances and 3 disk each this cause us to configure these alerts at a maximum of 621 instead of 69 times. That is a huge difference.
Would it be possible to tell SQL Monitor that a specific alert is an “Instance configure alert” instead of a Host alert and that it should overrides the Host alerts? Alternatively, some other solution.
Thanks! /Ted
Ted Bergkvist
shared this idea
-
Ted Bergkvist
commented
Hi Sybil
These are not VMs its mountpints in a clustered installation. These disks can reside on any of the servers in a cluster and has to be reconfigure when they are moved to a new cluster node. See the attached pic then you will understand what I mean. -
Hi Ted,
I'm Sybil, a product designer for the SQL Monitor Team. Thanks for your question.
The Monitor team are wondering if you mean custom alerts for disks that are mounted in the vm, when the vm is migrated to a new host?
I guess we are trying to understand where these disks are and why you'd like want the alerts to follow them.
For e.g. if I migrate a VM to a new host the hardware might be entirely different, so why would the alerts be the same?
Thanks
-
Anonymous
commented
Finally!
