VMware vSphere 5.0 server virtualization practice series (10): monitors resource usage]
In the previous blog post, we set up resource management in vSphere 5.0, while the virtual machines and hosts running in the online production environment still have various potential problems, VMware vCenter Alarms can be used to monitor resource usage, guard against various potential problems in the environment, shorten event response time, and prevent faults or VM performance degradation.
It is not difficult to set and manage VMware vCenter alarms, but several terms and concepts should be known before you start.
| VCenter alarms All objects in the vSphere environment have an available Alarms tab. On this tab, you can see the basic alarm, such as shutting down the host or VM) to stop it from exhausting resources. In most cases, these alarms are too common and need to be configured to monitor them more effectively. When using VMware vCenter alarms, it is important to determine the alert range. You can create alarms on a data center, cluster, host, or even a VM. This allows you to create more extensive or specific alerts. For example, if you create an alarm in a cluster, it applies to all hosts on the cluster and VMS on all hosts. However, if you create an alarm for a VM, it can only apply to this VM. Different Alarms can be used to meet different needs. For example, you can create alarms at the highest level in the data center, including all clusters, hosts, and VMS. If the available RAM on any VM drops to less than 20%, an alarm is triggered. But the 20% mark may not be suitable for the VMS we want to keep a close eye on. You can set an alarm to trigger when RAM is less than 30% on a VM. |
To define an alarm for a specific object, such as a host, you must first select an object. Click define on the Alarms tab to view the alarm list that has been set. To set the attributes of an alarm, you can double-click it from the list to display a window containing four tabs. These four tabs contain different attributes of the alarm, such as triggering alert items, how logs are recorded, and vSphere actions when an alert is triggered.
VSphere provides some default alarms, and here we create the alarms we actually need. Then, you can precisely define the actions that occur when an alarm is triggered.
You can set alarms when you right-click an object. Name the alarm on the General tab. On the Triggers tab, click Add to Add an alert trigger. If an alarm is added to the host, the default trigger type is the percentage of CPU usage. If the CPU usage of the host exceeds a certain percentage, the selected alarm is triggered.
After the trigger is selected, other attributes are created. First, select the alarm status. Generally, when the resource usage is higher than or below the selected threshold, you can set an alarm to trigger. Set the time when the alarm is triggered and the alarm is more serious after the alarm status is selected. Set the status duration for both. When the CPU usage exceeds 75% for more than 5 minutes, a warning is triggered. If the CPU usage exceeds 90%, an alarm is triggered.
The most important part of an alarm is its trigger. A specific trigger type applies to different objects in the environment, including disk usage, memory usage, and Power status.
After determining the alert trigger time, you also need to determine the Actions that should occur in vSphere on the Actions tab. The default action is to send a notification email Based on the SNMP network management tool, which is very important ).
You can also set the action after the alarm is triggered, such as entering maintenance mode, restarting the host, or running commands. At the same time, make sure to set the expected alarm for the configuration field. For example, to send a notification email, enter the email address in the configuration field to send the notification email.
This article from the "second O & M station" blog, please be sure to keep this source http://300second.blog.51cto.com/7582/1105035