Team A
[ZBXNEXT-1899] Threading email notifications about the same trigger (In-Reply-To) Created: 2013 Sep 10 Updated: 2024 Apr 10 Resolved: 2020 May 11 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | API (A), Frontend (F), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0beta2, 5.0 (plan) |
| Type: | New Feature Request | Priority: | Minor |
| Reporter: | Pavel | Assignee: | Andris Zeila |
| Resolution: | Fixed | Votes: | 17 |
| Labels: | alerts, email, grouping | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | Team A |
| Team: | Team A |
| Sprint: | Sprint 63 (Apr 2020), Sprint 64 (May 2020) |
| Story Points: | 2 |
| Description |
|
It will be good to put "In-Reply-To" and "References" email header fields contained msgid of previous event related to the same trigger. In this case notifications about the same problem will be collected to single thread in mailbox. It's useful: user can easy see if there was recovery message for the alarm or not (and problem is still actual). For external script media this logic can be implemented by adding macro {EVENT.PREVIOUS.ID}. |
| Comments |
| Comment by richlv [ 2013 Sep 10 ] |
|
macro was handled in leaving this open for built-in message threading |
| Comment by Oleksii Zagorskyi [ 2016 Mar 15 ] |
|
ZBXNEXT-1204 could be related |
| Comment by Michael Mol [ 2017 Jun 19 ] |
|
This would be supremely helpful for my ticket management as well. Right now, anywhere I have Zabbix emailing my ticket tracker, I get a new ticket for both "PROBLEM" and "OK" events. That's...bad. Using In-Reply-To and References email headers would tidy that up immediately and cleanly. On a related note, having the References header able to reference alerts that are no longer sent (Say, A depends on B, A fails, alert on A is sent, then B fails, B's alert ought to have a References pointing at A's alert) would also be extremely useful for the same reasons. Or, heck, if I could specify headers to send, and use macros to define what gets added to those headers, I could trivially build all of this myself. |
| Comment by Andris Zeila [ 2020 Apr 27 ] |
|
Released
|
| Comment by Marina Generalova (Inactive) [ 2020 Apr 28 ] |
|
Documentation updated: |
| Comment by Oleksii Zagorskyi [ 2020 Aug 27 ] |
|
It does not work for Gmail, reported in |