[ZBX-2419] IT Services: Calculation of availability is incorrect when uptimes are applied Created: 2010 May 11 Updated: 2017 May 30 Resolved: 2011 Nov 27 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 1.8.2 |
Fix Version/s: | 1.8.10, 2.0.0 |
Type: | Incident report | Priority: | Blocker |
Reporter: | jsteckel | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | itservices | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny8 with Suhosin-Patch mod_perl/2.0.4 Perl/v5.10.0 |
Attachments: | screenshot-1.jpg screenshot-2.jpg screenshot-3.jpg | ||||||||
Issue Links: |
|
Description |
The following service alarms have been recorded for service with serviceid = 3: mysql> SELECT servicealarmid, serviceid, clock, from_unixtime( clock ), value FROM `service_alarms` where serviceid = 3;
---------------
--------------- Service with serviceid = 3 was configured according to picture 1. The IT services report (report3.php) with Period = Daily executed on 11 May 2010, 11:00, states results according to picture 2. With uptime defined only for mondays between 09:00 and 17:00 I would have expected the following results (10 May 2010 was on a monday): ------------
------------
------------ On 09 May and 11 May values for "OK" and "Downtime" are incorrect. On 10 May values for "OK", "Problems", "Downtime", "Percentage" as well as the font color of "SLA" are incorrect. If I take out any uptime or downtime configuration I get results as expected for the same report (executed on 11 May 2010, 10:42, see picture 3). |
Comments |
Comment by jsteckel [ 2010 Sep 20 ] |
Are there any plans to resolve this bug? |
Comment by Alexei Vladishev [ 2011 Nov 16 ] |
This issue is related to |
Comment by Alexander Vladishev [ 2011 Nov 27 ] |
Fixed in the development branch, rev. 23557. Backport from trunk ( |
Comment by Pavels Jelisejevs (Inactive) [ 2011 Dec 02 ] |
Please review my r23716 commit. Otherwise TESTED. |
Comment by Alexander Vladishev [ 2011 Dec 02 ] |
Fixed in version pre-1.8.10, revision 23724 |