Graphical steps of zabbix monitoring vmware exsi host

1. Enter the virtualization vcenter, log in with a browser (the client does not find a place to set it up), and create a new read-only user zabbix.

2. Log in to the vcenter client and authorize the newly created user as read-only

After authorization, you can log in with the new account to test it.

3. Enable the Managed Object Browser (MOB) function of the exsi host. It is enabled by default if it is not enabled.

Go to the web client host system advanced settings to open

Config.HostAgent.plugins.solo.enableMob

4. Open zabbix and configure the server parameters. Follow the following parameters and add them if they are not available.

vi /etc/zabbix/zabbix_server.conf

StartVMwareCollectors=5 #Number of monitoring processes enabled VMwareFrequency=60 #Frequency for collecting new data VMwarePerfFrequency=60 #Frequency for collecting performance data VMwareCacheSize=80M #Cache size VMwareTimeout=10 #Wait for the vmware server to respond

Restart the service:

systemctl restart zabbix-server

5. Test whether you can connect to vcenter

curl -i -k --data “” http://< VMware ESXi >/sdk

6. Open the zabbix homepage to add a host

Add login information in the macro, including URL, login name and password.

{$URL}
{$USERNAME}
{$PASSWORD}

Note: You will see many hosts after a while. The addition of hosts is fully automatic, relying on the automatic discovery in vcenter. If VMS is turned off, you will not be able to add virtual machines in virtualization. Hypervisors are used to discover and add exsi hosts. Select automatic discovery and enable items according to your monitoring content. All items are enabled by default.

The words starting with discover represent hosts that are automatically discovered by vcenter.

7. Enter Detection-Latest Data to check whether the monitoring host has obtained the data.

8. Create a memory trigger. Set the alarm to be triggered when it exceeds 75%. My single host has 400G memory, so the threshold is set to be greater than 300G to trigger the alarm.

9. You can test whether the alarm can be triggered. According to the latest detected data, lower the threshold to trigger it.

10. Email alarm monitoring
10.1 First, you need to have two mailboxes, one for sending messages and one for receiving messages. The mailbox for sending emails needs to use the client authorization code to log in. Please refer to Zabbix to add email alarm settings
10.2 After the mailbox is created, follow the steps 5 and 6 in the blog above to fill in the information of the alarm media mailbox and create a new user and mailbox to receive the information. After adding, create an action

10.3 Lower the threshold and wait for email alerts Example: I changed the memory trigger to 30G

Alert received, but no email sent

Zabbix email alarm, several reasons for not sending emails:
1. The account authentication of Zabbix email failed, the authorization code was not used to log in, or other information was wrong. You need to check it. Please refer to points 2, 3, and 4 to set up a mail server for testing when adding email alarm settings in Zabbix.
2. There is a problem with permissions. This is really a pitfall. In zabbix, different user permissions are divided into users, administrators, and super administrators. Simply put, if you are a super administrator, you will have permissions for all groups. If you are an administrator or user, you must authorize your user, which is very troublesome, so just authorize the super administrator directly.
3. There is another reason. If the action you add is after the alarm is triggered, no email will be sent. Therefore, the trigger selected when setting the action should be healthy. If it is for testing, it is best to change the trigger threshold after adding the action.

The above is the details of zabbix monitoring vmware exsi host. For more information about zabbix monitoring exsi host, please pay attention to other related articles on 123WORDPRESS.COM!