Updated to v0.8

Added support for Slack message threading (to attach Zabbix acknowledgement notifications ) Described best practices on using --nofork in README

Features Include:

All:

• All configuration is done in Zabbix web-interface(no config files anywhere)
• UTF8 supported
• HTTPS/HTTP proxy supported(see how at the end)

Slack:

• Color coding events depending on Trigger Status and Severity
• Recovery and acknowledgements from Zabbix will be posted as new messages (--slack_mode=event)
• Acknowledgements(Zabbix 3.4+) will be attached as replies to Slack message thread. Recovery message from Zabbix will update and then delete initial problem message as well as all acknowledgements. .(--slack_mode=alarm)
• Acknowledgements will be attached as replies to Slack message thread. Recovery message from Zabbix will update initial message.(--slack_mode=alarm-no-delete)
• JSON can be used to compose Slack messages. See Slack message attachments

HipChat:

• Color coding events depending on Trigger Status and Severity
• HTML or plain text can be used to format HipChat messages.
• JSON can be used to compose messages. See HipChat API

PagerDuty:

• Recovery message from Zabbix will resolve already created incident in PagerDuty
• Acknowledgements will be added already created incidenents
• JSON can be used to compose messages. See PagerDuty API here and here

About using --nofork If you have Zabbix 3.4 or newer, it recommended to use --nofork option from Zabbix. This will give you an ability to see errors in Zabbix if something goes wrong: image

Just make sure you enabled concurrent sessions in Zabbix. Use --nofork with care if you use Slack with --slack_mode=alarm, since script then sleeps for 30s before removing messages from Slack.