[ZBX-25688] Symptom problem does not convert to cause after the initial cause was solved Created: 2024 Dec 06  Updated: 2024 Dec 10  Resolved: 2024 Dec 09

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 7.0.6
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Maksym Buz Assignee: Zabbix Development Team
Resolution: Won't fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2024-12-06-13-56-42-289.png     PNG File orphaned symptom - will go unnoticed without proper filtering.png    
Issue Links:
Duplicate
Sprint: Support backlog

 Description   

Steps to reproduce:

  • Generate any two problems
  • Mark one of it as a symptom for another
  • Resolve the cause problem
  • The symptom problem remains in that state (it's not reverting back to a cause).

Result:

  • By default (unless the "Show symptoms" checkbox is explicitly set in the filter), this problem does not appear on the problem screen.
  • Even if this checkbox is set and the problem is visible, there is no indication of which problem was its cause (since the cause is already resolved).
  • These events do not appear in the audit records (Report → Audit Log), meaning there is no visibility of who marked the problem as a "symptom" or which problem was marked as the "cause."

Expected

  • After the cause problem is resolved - all it's symptom problems became a separate cause problems
  • Changing the problem to symptom/cause logged in the Audit Log. 


 Comments   
Comment by Nicola Mauri [ 2024 Dec 10 ]

sasha is it possible to explain why this issue was marked as "Won't fix"? Is this behaviour "by design"? Can be it added to the documentation?
Thanks.

Comment by Alexander Vladishev [ 2024 Dec 10 ]

Conversion of symptoms to causes:

The decision to close this ticket as "Won't Fix" was made for the following reasons:

  1. This functionality works as it was intended to be implemented.
  2. Changing the behavior in minor versions could negatively impact the user experience.

We have taken this into account and may adjust the behavior of closing the cause event in one of the upcoming major releases.

Audit:

The audit has never covered operations with events. Such information is stored in the action history of each event.

Generated at Sun Apr 06 09:08:00 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.