[ZBXNEXT-1318] [Patch] Introduce a new macro to allow for e-mail threading (original problem's eventid) Created: 2012 Jul 15 Updated: 2013 Jan 29 Resolved: 2013 Jan 29 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | 2.0.2 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Volker Fröhlich | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 1 |
Labels: | threading, tracker, trivial | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | zabbix-2.0.1-probmacro.patch | ||||||||
Issue Links: |
|
Description |
Primary goal: Thread corresponding problem/ok events in e-mails Concept: A media script is used for messaging and recovery messages are enabled. In the case of a recovery message, the script parses the message body for a unique identifier, namely the eventid of the preceding problem event. This unique identifier is used as Message-Id in the mail header. Benefit: E-mail clients can present corresponding events in a threaded way. Users can easier recognize the current state of an issue – especially if they lack access to the frontend for some reason. Implementation:
Open questions:
Other possible applications:
|
Comments |
Comment by Oleksii Zagorskyi [ 2012 Jul 16 ] |
Similar to a |
Comment by Garth Dahlstrom [ 2012 Sep 25 ] |
Is there any chance that either this or I have to get a new Zabbix server instance (planning to use 2.0.2) up and running and the procedure is going to be complicated by the fact that the fellow doing it is going to have to build Zabbix from source to get the {ESC.ORIGIN.EVENT.ID} macro that we need for our ticketing email templates (big PITA). If you guys didn't want to merge the patch attached to |
Comment by Alexei Vladishev [ 2013 Jan 29 ] |
It is a duplicate of |