[ZBXNEXT-7964] Cause and symptom events Created: 2022 Sep 07  Updated: 2024 Oct 29  Resolved: 2023 Jan 31

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: None
Fix Version/s: 6.4.0beta6, 6.4 (plan)

Type: Change Request Priority: Trivial
Reporter: Alexei Vladishev Assignee: Ivo Kurzemnieks
Resolution: Fixed Votes: 8
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PDF File ACC_ZBXNEXT-7964_cause_and_symptom_events.pdf     PNG File Screenshot (23).png     PNG File Screenshot 2022-11-21 at 19.24.46.png     PNG File Screenshot 2022-11-21 at 19.27.25.png     PNG File Screenshot 2022-11-21 at 19.40.09.png     PNG File Screenshot 2022-11-21 at 19.40.31.png     PNG File chrome-row.png     Text File codingstyle.patch     Text File collapse-and-expand.patch     PNG File disabled-actions.png     PNG File line1.png     PNG File line2.png     PNG File missing-lines-in-times-column.png     PNG File notvisible-rankchange.png     PNG File npm-netpath-detail.png     PNG File time-header.png     PNG File widgetcolumn-after.png     PNG File widgetcolumn-before.png    
Issue Links:
Causes
causes ZBX-22675 Problem with housekeeper - table 'pro... Closed
causes ZBX-22280 Unable to open symptom list if it con... Closed
causes ZBX-22808 Problem popup list has a displaced ho... Closed
causes ZBX-22889 Performance problems due to missing p... Closed
causes ZBX-25465 Action notification is not being sent... Closed
Duplicate
Sub-task
Sub-Tasks:
Key
 Summary
 Type
 Status
 Assignee
ZBXNEXT-7993 Server side changes to implement Caus... Change Request (Sub-task) Closed Mihails Prihodko  
Team: Team B
Sprint: Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023)
Story Points: 23

 Description   

Currently Zabbix does not have a notion of a hierachy of events. It is impossible to tell what event caused what.

It is proposed to mark all events as "cause" and "symptom", where one "cause" event may have a number of corresponding "symptom" events. This way we can see clearly what caused what and we can also filter out symptom events to get an uncluttered view of root-cause problems.

 Comments   
Comment by Dimitri Bellini [ 2022 Sep 28 ]

Fantastic news, I hope to see on Zabbix 6.4.
My dream is to reach to something like the below screenshot

Thanks so much

Comment by Mihails Prihodko [ 2022 Oct 17 ]

dimitri.bellini, I added the acceptance criteria for this task in attachment: ACC_ZBXNEXT-7964_cause_and_symptom_events.pdf. It provides some more information regarding what is planned in this task.

Comment by Dimitri Bellini [ 2022 Oct 25 ]

Dear Mihails,
I hope this is the first piece of a more complex feature that will be released on 7.0
Thanks so much

Comment by Ivo Kurzemnieks [ 2022 Nov 16 ]

Implemented in development branch feature/ZBXNEXT-7964-6.3

Comment by Martins Valkovskis [ 2023 Jan 10 ]

Updated documentation:

Comment by Ivo Kurzemnieks [ 2023 Jan 11 ]

Updated API documentation:

Comment by Michael Veksler [ 2023 Jan 12 ]

Available in:

Generated at Sun Apr 20 21:34:23 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.