[ZBX-17188] Problems with negative duration are considered by parent service SLA calcullations Created: 2020 Jan 16  Updated: 2023 Oct 07

Status: Open
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 4.0.17rc1, 4.4.5rc1, 5.0.0alpha1
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Sergejs Olonkins Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 1
Labels: SLA, services
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: GIF File negative_duration_parent_SLA.gif    
Issue Links:
Sub-task
part of ZBX-21965 Incorrect SLA calculation Confirmed
part of ZBX-21967 Incorrect problem duration calculation Confirmed
part of ZBX-13197 Wrong SLA calculation Need info
part of ZBX-16543 Service with algorithm "if all childr... Postponed

 Description   

Problem description: Let's say there is a parent service, that goes in problem status if one of its child services is in status problem. At least 2 of its child services, that are based on triggers, are in problem status, one of which was set in this status by an event with future timestamp (corresponding problem has negative duration). If all child services change their status to OK except for the one with the future dated event, the problem with negative duration is not considered in calculation of the child service SLA, but still is considered in calculation of parent service SLA.
According to ZBX-14592, Problems with negative duration should not affect SLA calculations.

Steps to reproduce:

  1. Create a host with 2 trapper items
  2. Create a trigger for each item, all triggers should have different severities (Warning, Average)
  3. Create a Parent service: set "Start calculation algorithm" to "Problem, if at least one child has a problem" and set the "Calculate SLA" option.
  4. Create 2 child services with same setup, specify 1 previously created trigger for each service.
  5. Set the trigger with lower priority (and the corresponding child service) to status "Problem" by a problem events with current timestamp - make sure that the parent service is now also in status "Problem".
  6. Set the 2nd trigger with higher priority (and the corresponding child service) to status "Problem" by a future dated event. Verify that a problem with negative duration is produced.
  7. Set the 1st triggers with lower priority (and the corresponding child services) to status OK and check SLA for all 3 services.

Result: SLA of both child services is not decreasing (as one is in status ok, but the problem for the other is triggered by an event with future timestamp), but the SLA of the parent service continues to decrease.

Expected: problems with negative duration should not influence SLA calculations

Example:



 Comments   
Comment by Vladislavs Sokurenko [ 2023 Oct 07 ]

Also see:
ZBX-13197
ZBX-16543
ZBX-21967
ZBX-21965

Comment by dimir [ 2023 Oct 07 ]

Quoting: "This issue was raised during conference, it appears that it worked before and was broken later."

Generated at Tue May 06 08:14:54 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.