[ZBX-13009] Availability report shows incorrect SLA Created: 2017 Nov 09  Updated: 2024 Apr 10  Resolved: 2018 Nov 15

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 3.2.9
Fix Version/s: 3.0.24rc1, 4.0.2rc1, 4.2.0alpha1, 4.2 (plan)

Type: Problem report Priority: Major
Reporter: aleksandr.pylkov Assignee: Gregory Chalenko
Resolution: Fixed Votes: 1
Labels: availabilityreport
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File avReport.jpg     JPEG File avReport2.jpg     JPEG File avReport2017.jpg     JPEG File problems.jpg     JPEG File trigger.jpg    
Team: Team D
Team: Team D
Sprint: Sprint 24, Sprint 25, Sprint 26, Sprint 27, Sprint 28, Sprint 29, Sprint 30, Sprint 31, Sprint 32, Sprint 33, Sprint 34, Sprint 35, Sprint 36, Sprint 37, Sprint 38, Sprint 39, Sprint 40, Sprint 41, Sprint 42, Sprint 43, Sprint 44, Sprint 45, Sprint 46, Nov 2018
Story Points: 1

 Description   

We are monitoring our service by response code 200. In October we have an outage for ~ 2 mins. But availability montly report shows that we have SLA ~ 95%. It is incorrect.
Have a look at screenshot avReport2.jpeg, as you can see SLA is 100% for the month period except for last hour. But if we include this last hour (when we have outage for 2 mins - problems.jpeg) SLA will be ~95% (avReport.jpeg)



 Comments   
Comment by Vladislavs Sokurenko [ 2017 Nov 09 ]

Maybe there were other triggers that affected SLA calculation, do you have a tree structure ? Are many triggers used for it ?

Comment by aleksandr.pylkov [ 2017 Nov 09 ]

Vso we have just one trigger. See screenshot trigger.jpg

Comment by Vladislavs Sokurenko [ 2017 Nov 09 ]

I am sorry, is it just availability report page that shows incorrect ? Other pages work as expected ? For example what does monitoring->itservices show ?

Comment by aleksandr.pylkov [ 2017 Nov 09 ]

Vso we do not use IT services (and we do not calculate SLA there).

Comment by Gregory Chalenko [ 2018 Jan 02 ]

(1) No translation strings changes.

iivs CLOSED

Comment by Gregory Chalenko [ 2018 Nov 14 ]

Fixed in:

  • 3.0.24rc1 r86833
  • 4.0.2rc1 r86886
  • 4.2.0alpha1 (trunk) r86887
Generated at Fri Apr 19 06:59:38 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.