From: Ben C. <Be...@cl...> - 2004-09-06 07:26:58
|
Tim, I'll take a close look. The time span on the report is calculated from the event to the next=20 changed event. It might be that the report is from the last to he curren= t. There will be another version soon, I will ensure that this bug is remove= d. Regards, Ben. Tim Wuyts wrote: > All, >=20 > I'm having a look at the raw history report, and I found something pecu= liar. Below is an example output from the report: > <OUTPUT> > Status Last Check =E2=88=86 Time Plugin Output=20 > UP 2004-09-03 11:39:01 0 days 01:40:10 PING OK - Packet loss =3D= 0%, RTA =3D 5.10 ms =20 > WARNING 2004-09-03 13:19:11 0 days 00:00:50 PING WARNING - Packet l= oss =3D 20%, RTA =3D 2.20 ms =20 > UP 2004-09-03 13:20:01 0 days 03:34:00 PING OK - Packet loss =3D= 0%, RTA =3D 2.30 ms =20 >=20 > <graph> >=20 > State Count Percent Time=20 > UP 64 98.462% 0 days 05:10:09=20 > WARNING 1 1.538% 0 days 00:04:50=20 > CRITICAL 0 0.000% 0 days 00:00:00=20 > UNKNOWN 0 0.000% 0 days 00:00:00=20 >=20 > Start: 2004-09-03 11:39:01 End: 2004-09-03 16:54:01=20 > Span: 0 days 05:15:00 Mean =E2=88=86 Time: 0 days 01:45:00 =20 > </OUTPUT> >=20 > There seems to be a discrepancy between the timespans calculated in the= events list, and the one in the summary: > UP =3D 01:40:10 + 03:34:00 =3D 5:14:10 vs 05:10:09 > WARNING =3D 00:00:50 vs 00:04:50 >=20 > Apparently the timespans are calculated differently in the summary than= for the individual event changes. >=20 > Tim. >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_idP47&alloc_id=10808&op=EF=BF=BDk > _______________________________________________ > Perfparse-users mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-users >=20 |