image-2020-02-05-15-34-41-427.png
image-2020-02-05-15-49-30-203.png
[ZBX-17271] Trigger Correlation behaves differently with LLD Triggers Created: 2020 Feb 05 Updated: 2020 Feb 13 Resolved: 2020 Feb 13 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 4.4.4 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Grant Ashton | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
image-2020-02-05-15-34-41-427.png
image-2020-02-05-15-49-30-203.png
|
| Description |
|
A static template trigger setup to use trigger correlation, results in a unique event per unique AlarmKey, even if duplicate item values are received. (This is good, and expected) However when an identical LLD trigger is create (expression referencing an LLD item), it results in duplicate events, if the same item value is received multiple times, with duplicate AlarmKey tags.
The items being referenced in the trigger expression are text, syslogs. The trigger looks for stopped, and the recovery looks for started. The AlarmKey tag is extracted from the log message. I suggest replicating a basic example of this in your test environment, the behaviour will be quite obvious. |
| Comments |
| Comment by Grant Ashton [ 2020 Feb 10 ] |
|
After further investigation, it appears this is actually normal behaviour for both LLD and normal triggers. Unfortunately the real issue appears to be that it is not possible to deduplicate the problem events to prevent multiple duplicates, which would be a nice feature to have. Ideally a deduplication on one or more tags. Similar to how trigger correlation uses them. The issue can be closed. |
