Detailed explanation of how Zabbix3.0.2 uses external python scripts to implement email alarms

1, find the default path where the script is stored (I put it under the default path, if you want to change to another path, modify the zabbix_server.conf configuration file)

/usr/local/zabbix-server/ share/zabbix/alertscripts script storage path

2, create a mail.py file in the directory, script reference:

cd /usr/local/zabbix-server/share/zabbix/alertscripts

vim mail.py

#!/usr/bin/python

#coding:utf-8

#author: itnihao

#mail: itnihao@qq.com

#url:https://github.com/itnihao/zabbix-book/edit/master/06-chapter/zabbix_sendmail_v2.py Script can be directly down modified and copied Format problems will occur~

import smtplib

from email.mime.text import MIMEText

import os

import argparse

import logging

import datetime

#QQ enterprise

#smtp_server = 'smtp.exmail.qq.com'

#smtp_port = 25

#smtp_user = 'itnihao_zabbix@itnihao.com'

#smtp_pass = '1234567890'

#163 Mail

#smtp_server = 'smtp.163.com'

#smtp_port = 25

#smtp_user = 'itnihao_zabbix@163.com'

#smtp_pass = '1234567890'

#QQ Mail

smtp_server ='smtp.qq.com'

smtp_port = 25

smtp_user ='itnihao_zabbix@qq.com'

smtp_pass ='1234567890'

def send_mail(mail_to,subject,content):

msg = MIMEText(content,_subtype='plain', _charset='utf-8')

msg['Subject'] = unicode(subject,'UTF-8')

msg['From'] = smtp_user

msg['to'] = mail_to

global sendstatus

global senderr

try:

if smtp_port == 465:

smtp = smtplib.SMTP_SSL()

else:

smtp = smtplib.SMTP()

smtp.connect(smtp_server,smtp_port)

smtp.login(smtp_user,smtp_pass)

smtp.send mail(smtp_user,mail_to ,msg.as_string())

smtp.close()

print 'send ok'

sendstatus = True

except Exception,e:

senderr=str(e)

print senderr

sendstatus = False

def logwrite(sendstatus,mail_to,content):

logpath='/var/log/zabbix/alert'

if not sendstatus:

content = senderr

if not os.path.isdir(logpath):

os.makedirs(logpath)

t=datetime.datetime.now()

daytime=t.strftime('%Y-%m-%d')

daylogfile=logpath+'/'+str(daytime)+'.log'

logging.basicConfig(filename=daylogfile,level=logging.DEBUG)

os.system( 'chown zabbix.zabbix {0}'.format(daylogfile))

logging.info('*'*130)

logging.debug(str(t)+' mail send to {0},content is :\n {1}'.format(mail_to,content))

if __name__ == "__main__":

parser = argparse.ArgumentParser(description=' Send mail to user for zabbix alerting')

parser.add_argument('mail_to',action="store", help='The address of the E-mail that send to user ')

parser.add_argument('subject',action="store", help='The subject of the E-mail')

parser.add_argument('content',action="store", help=' The content of the E-mail')

args = parser.parse_args()

mail_to=args.mail_to

subject=args.subject

content=args.content

send _mail(mail_to,subject,content)

logwrite(sendstatus,mail_to,content)

3, modify the permissions of the script

# chown zabbix.zabbix mail.py

# chmod 775 mail.py

4, zabbix web configuration

Select the media type in the configuration and create a media type

Fill in the following information, type selection script, you need to fill in the following 3 parameters for zabbix3.0.

Create a user or set an alarm in the admin user

What is added here is after a failure occurs The email to which the email is notified is the recipient.

Create an action to implement email alarm, in the configuration-Action-create action

(My picture is different from the template given below, it is recommended Using a template, because the server I use is not in China, all email titles will be garbled. So I shortened the title in this picture)

##Name:

.

Action-Email

Default subject:

Fault {TRIGGER.STATUS}, Server: {HOSTNAME1} Occurred: {TRIGGER.NAME} fault!

Default message :

Alarm host: {HOSTNAME1}

Alarm time: {EVENT.DATE} {EVENT.TIME}

Alarm level: {TRIGGER.SEVERITY}

Alarm information: {TRIGGER.NAME}

Alarm item:{TRIGGER.KEY1}

Problem details:{ITEM.NAME}:{ITEM.VALUE}

Current status: {TRIGGER.STATUS}:{ITEM.VALUE1}

Event ID:{EVENT.ID}

Please go to Montoring-Events to view details.

Recovery subject:

Recover {TRIGGER.STATUS}, server: {HOSTNAME1}: {TRIGGER.NAME} has been recovered!

Recovery message:

Alarm host: {HOSTNAME1}

Alarm time: {EVENT.DATE} {EVENT.TIME}

Alarm level: {TRIGGER.SEVERITY}

Alarm information: { TRIGGER.NAME}

Alarm item:{TRIGGER.KEY1}

Problem details:{ITEM.NAME}:{ITEM.VALUE}

Current status:{TRIGGER. STATUS}:{ITEM.VALUE1}

Event ID:{EVENT.ID}

The alarm has been restored, please relax.

Here you should pay attention to the type of operation, the message sent, and the script of the message. You must choose the right one.

#5, test zabbix to send emails

Find an agent client and stop it. Then look at the alarm email~

After Kill, you can see that it has been successfully sent~

Note: Zabbix's alarm is usually sent once every 5 minutes. For example: If it stops at 16:20, you will receive the fault email at 16:25 and it will be processed at 16:30. The recovery information can be received at 16:35~ …

6. Summary

I am using ubuntu 16.4 here system, I first tried to use mailx to send, but later I couldn’t install some library files, and then I switched to other methods and couldn’t receive emails. Finally, I decided to use an external python script to achieve ~· The Ubuntu system has many software dependencies that do not come with its own environment. .apt-get is really not easy to use. When using the 126 mailbox, the client authorization code cannot be logged in in the python script. The QQ mailbox can only be used by yourself. The last choice is the company's corporate mailbox. However, because zabbix frequently sends emails, many of them are thrown into the trash... Finally, I forwarded them to the QQ mailbox in the corporate mailbox.

Ubuntu is fine for development and learning, but there are still many problems when used as a server.

Correct posture: centos+zabbix+corporate mailbox. If you have the opportunity to write a follow-up article, wechat alarm in zabbix.

The above is the detailed content of Detailed explanation of how Zabbix3.0.2 uses external python scripts to implement email alarms. For more information, please follow other related articles on the PHP Chinese website!