Hello guys,
I am new to Zabbix and configuring it to my closed network environment.
My network is closed - the only white list destinations are allowed to access.
I have deployed zabbix 5.2 in the network, and monitoring several things in the same network. It works as well.
However Slack noti doesnt look well.
I set up Slack notification, through a http proxy to access SlackAPI (outside of my network), the proxy (not zabbix proxy, but http proxy) is set to Slack script in the media type of Slack.
And testing slack in the media type menu, the slack message is successfully sent.
But in real notification, the thing is different:
- Actually slack message is sent as well
- However Zabbix logs it as "time out" in the action log page, and zabbix retries 2 more times therefore totally 3 slack messages are sent.
- Also, Resolved message does not be sent, it is logged as "channel not founnd" in the action log page.
Once I have set http_proxy and https_proxy environment to zabbix-server then the notification works.
I think this is a bug. Where can I log this bug?
One more question,
If I set http_proxy to zabbix-server, then will it be effected all of monitoring resources related of HTTP?
If then I have to unset http_proxy to zabbix-server and find any other solution or bug-fix of slack notification issue.
I am new to Zabbix and configuring it to my closed network environment.
My network is closed - the only white list destinations are allowed to access.
I have deployed zabbix 5.2 in the network, and monitoring several things in the same network. It works as well.
However Slack noti doesnt look well.
I set up Slack notification, through a http proxy to access SlackAPI (outside of my network), the proxy (not zabbix proxy, but http proxy) is set to Slack script in the media type of Slack.
And testing slack in the media type menu, the slack message is successfully sent.
But in real notification, the thing is different:
- Actually slack message is sent as well
- However Zabbix logs it as "time out" in the action log page, and zabbix retries 2 more times therefore totally 3 slack messages are sent.
- Also, Resolved message does not be sent, it is logged as "channel not founnd" in the action log page.
Once I have set http_proxy and https_proxy environment to zabbix-server then the notification works.
I think this is a bug. Where can I log this bug?
One more question,
If I set http_proxy to zabbix-server, then will it be effected all of monitoring resources related of HTTP?
If then I have to unset http_proxy to zabbix-server and find any other solution or bug-fix of slack notification issue.