Created
May 15, 2020 17:59
-
-
Save cherts/04a0905d53c136ee8d5a81c4af93bc9d to your computer and use it in GitHub Desktop.
Fixed use http proxy for official media telegram in Zabbix 5.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?xml version="1.0" encoding="UTF-8"?> | |
| <zabbix_export> | |
| <version>5.0</version> | |
| <date>2020-05-15T17:57:20Z</date> | |
| <media_types> | |
| <media_type> | |
| <name>Telegram</name> | |
| <type>WEBHOOK</type> | |
| <parameters> | |
| <parameter> | |
| <name>HTTPProxy</name> | |
| <value/> | |
| </parameter> | |
| <parameter> | |
| <name>Message</name> | |
| <value>{ALERT.MESSAGE}</value> | |
| </parameter> | |
| <parameter> | |
| <name>ParseMode</name> | |
| <value/> | |
| </parameter> | |
| <parameter> | |
| <name>Subject</name> | |
| <value>{ALERT.SUBJECT}</value> | |
| </parameter> | |
| <parameter> | |
| <name>To</name> | |
| <value>{ALERT.SENDTO}</value> | |
| </parameter> | |
| <parameter> | |
| <name>Token</name> | |
| <value><PLACE YOUR TOKEN></value> | |
| </parameter> | |
| </parameters> | |
| <script>var Telegram = { | |
| token: null, | |
| to: null, | |
| message: null, | |
| proxy: null, | |
| parse_mode: null, | |
| | |
| sendMessage: function() { | |
| var params = { | |
| chat_id: Telegram.to, | |
| text: Telegram.message, | |
| disable_web_page_preview: true, | |
| disable_notification: false | |
| }, | |
| data, | |
| response, | |
| request = new CurlHttpRequest(), | |
| url = 'https://api.telegram.org/bot' + Telegram.token + '/sendMessage'; | |
| | |
| if (Telegram.parse_mode !== null) { | |
| params['parse_mode'] = Telegram.parse_mode; | |
| } | |
| | |
| request.AddHeader('Content-Type: application/json'); | |
| | |
| if (Telegram.proxy !== null) { | |
| request.SetProxy(Telegram.proxy); | |
| } | |
| | |
| data = JSON.stringify(params); | |
| | |
| // Remove replace() function if you want to see the exposed token in the log file. | |
| Zabbix.Log(4, '[Telegram Webhook] URL: ' + url.replace(Telegram.token, '<TOKEN>')); | |
| Zabbix.Log(4, '[Telegram Webhook] params: ' + data); | |
| response = request.Post(url, data); | |
| Zabbix.Log(4, '[Telegram Webhook] HTTP code: ' + request.Status()); | |
| | |
| try { | |
| response = JSON.parse(response); | |
| } | |
| catch (error) { | |
| response = null; | |
| } | |
| | |
| if (request.Status() !== 200 || typeof response.ok !== 'boolean' || response.ok !== true) { | |
| if (typeof response.description === 'string') { | |
| throw response.description; | |
| } | |
| else { | |
| throw 'Unknown error. Check debug log for more information.' | |
| } | |
| } | |
| } | |
| } | |
| | |
| try { | |
| var params = JSON.parse(value); | |
| | |
| if (typeof params.Token === 'undefined') { | |
| throw 'Incorrect value is given for parameter "Token": parameter is missing'; | |
| } | |
| | |
| Telegram.token = params.Token; | |
| | |
| if (params.HTTPProxy) { | |
| Telegram.proxy = params.HTTPProxy; | |
| Zabbix.Log(4, '[Telegram Webhook] Use proxy: ' + params.HTTPProxy); | |
| } | |
| | |
| if (['Markdown', 'HTML', 'MarkdownV2'].indexOf(params.ParseMode) !== -1) { | |
| Telegram.parse_mode = params.ParseMode; | |
| } | |
| | |
| Telegram.to = params.To; | |
| Telegram.message = params.Subject + '\n' + params.Message; | |
| Telegram.sendMessage(); | |
| | |
| return 'OK'; | |
| } | |
| catch (error) { | |
| Zabbix.Log(4, '[Telegram Webhook] notification failed: ' + error); | |
| throw 'Sending failed: ' + error + '.'; | |
| }</script> | |
| <timeout>10s</timeout> | |
| <description>https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/telegram | |
| | |
| 1. Register bot: send "/newbot" to @BotFather and follow instructions | |
| 2. Copy and paste the obtained token into the "Token" field above | |
| 3. If you want to send personal notifications, you need to get chat id of the user you want to send messages to: | |
| 3.1. Send "/getid" to "@myidbot" in Telegram messenger | |
| 3.2. Copy returned chat id and save it in the "Telegram Webhook" media for the user | |
| 3.3. Ask the user to send "/start" to your bot (Telegram bot won't send anything to the user without it) | |
| 4. If you want to send group notifications, you need to get group id of the group you want to send messages to: | |
| 4.1. Add "@myidbot" to your group | |
| 4.2. Send "/getgroupid@myidbot" in your group | |
| 4.3. Copy returned group id save it in the "Telegram Webhook" media for the user you created for group notifications | |
| 4.4. Send "/start@your_bot_name_here" in your group (Telegram bot won't send anything to the group without it)</description> | |
| <message_templates> | |
| <message_template> | |
| <event_source>TRIGGERS</event_source> | |
| <operation_mode>PROBLEM</operation_mode> | |
| <subject>Problem: {EVENT.NAME}</subject> | |
| <message>Problem started at {EVENT.TIME} on {EVENT.DATE} | |
| Problem name: {EVENT.NAME} | |
| Host: {HOST.NAME} | |
| Severity: {EVENT.SEVERITY} | |
| Operational data: {EVENT.OPDATA} | |
| Original problem ID: {EVENT.ID} | |
| {TRIGGER.URL}</message> | |
| </message_template> | |
| <message_template> | |
| <event_source>TRIGGERS</event_source> | |
| <operation_mode>RECOVERY</operation_mode> | |
| <subject>Resolved in {EVENT.DURATION}: {EVENT.NAME}</subject> | |
| <message>Problem has been resolved in {EVENT.DURATION} at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE} | |
| Problem name: {EVENT.NAME} | |
| Host: {HOST.NAME} | |
| Severity: {EVENT.SEVERITY} | |
| Original problem ID: {EVENT.ID} | |
| {TRIGGER.URL}</message> | |
| </message_template> | |
| <message_template> | |
| <event_source>TRIGGERS</event_source> | |
| <operation_mode>UPDATE</operation_mode> | |
| <subject>Updated problem: {EVENT.NAME}</subject> | |
| <message>{USER.FULLNAME} {EVENT.UPDATE.ACTION} problem at {EVENT.UPDATE.DATE} {EVENT.UPDATE.TIME}. | |
| {EVENT.UPDATE.MESSAGE} | |
| | |
| Current problem status is {EVENT.STATUS}, acknowledged: {EVENT.ACK.STATUS}.</message> | |
| </message_template> | |
| <message_template> | |
| <event_source>DISCOVERY</event_source> | |
| <operation_mode>PROBLEM</operation_mode> | |
| <subject>Discovery: {DISCOVERY.DEVICE.STATUS} {DISCOVERY.DEVICE.IPADDRESS}</subject> | |
| <message>Discovery rule: {DISCOVERY.RULE.NAME} | |
| | |
| Device IP: {DISCOVERY.DEVICE.IPADDRESS} | |
| Device DNS: {DISCOVERY.DEVICE.DNS} | |
| Device status: {DISCOVERY.DEVICE.STATUS} | |
| Device uptime: {DISCOVERY.DEVICE.UPTIME} | |
| | |
| Device service name: {DISCOVERY.SERVICE.NAME} | |
| Device service port: {DISCOVERY.SERVICE.PORT} | |
| Device service status: {DISCOVERY.SERVICE.STATUS} | |
| Device service uptime: {DISCOVERY.SERVICE.UPTIME}</message> | |
| </message_template> | |
| <message_template> | |
| <event_source>AUTOREGISTRATION</event_source> | |
| <operation_mode>PROBLEM</operation_mode> | |
| <subject>Autoregistration: {HOST.HOST}</subject> | |
| <message>Host name: {HOST.HOST} | |
| Host IP: {HOST.IP} | |
| Agent port: {HOST.PORT}</message> | |
| </message_template> | |
| </message_templates> | |
| </media_type> | |
| </media_types> | |
| </zabbix_export> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment