[ZBX-25422] Slack Integration Improvements Created: 2024 Oct 21 Updated: 2025 Mar 18 Resolved: 2025 Mar 18 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Templates (T) |
Affects Version/s: | 6.0.35, 7.0.5, 7.2.0alpha1 |
Fix Version/s: | None |
Type: | Patch request | Priority: | Major |
Reporter: | Robert Lech | Assignee: | Andrew Biba |
Resolution: | Duplicate | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Docker compose, official images |
Attachments: |
![]() |
Team: | |
Sprint: | Support backlog |
Story Points: | 1 |
Description |
The slack template that ships with zabbix has issues sending updates and resolved messages to multiple slack channels if the channel names are similar. eg. #zabbix and #zabbix-customer. Both channels will get the initial problem event but only one channel will get the updated resolve message. So instead of checking for a partial match (.includes), I'm checking for exact channel names (===). I also added support for service events with a default message to ping the channel. Probably not the most desirable for everyone but it works well for us. |
Comments |
Comment by Andrew Biba [ 2025 Mar 04 ] |
Fixed in task |