1, create alarm groups
2. Fill in the group information (permissions temporarily configure, self-depth study)
3, the group just created to view
4, create user alerts
5, fill in the user configuration information
6, the configuration of the alarm media rights
7, and then click Add to see a list of users created
8, create action
8.1, the new action triggering conditions
8.2, an editing operation, content editing is issued i.e., alarm
Alarm Host: {HOSTNAME1}
Alarm Time: {EVENT.DATE} {EVENT.TIME}
Alarm level: {TRIGGER.SEVERITY}
Alarms: {TRIGGER.NAME}
Alarm items: {TRIGGER.KEY1}
Issue Details: {ITEM.NAME}: {ITEM.VALUE}
Current Status: {TRIGGER.STATUS}: {ITEM.VALUE1}
Event ID: {EVENT.ID}
8.3, alarm when editing recovery
Recovery time problem: {EVENT.RECOVERY.DATE} {EVENT.RECOVERY.TIME}
Name of Problem: {EVENT.NAME}
Host: {HOST.NAME}
Level problem: {EVENT.SEVERITY}
Event ID: {EVENT.ID}
Event Status: {EVENT.RECOVERY.STATUS}
8.4, save
9, zabbix recommended to restart the service, I found that the test does not take effect, to take effect after the restart service varies (with the election)
[root@filestore-v2 ~]# /etc/init.d/zabbix_server restart
10, test warning is in effect
11, cell phone micro letter received issue a warning message
12, cell phone micro-channel issues a warning message recovery