Hi All,
We're using Hobbit to pretty much monitor most things - and it works fine. One of our sections likes to keep track of the availablility of their web page and they have been using hobbit for this and are happy with what it gives them, except for an anomally from last month. When the availability report is run for last month I get a green diamond (presuming this to mean that it's 100%). We know it's not 100% by simply clicking on the http diamond and performing a history of the service. Why doesn't the monthly report tell us what is obviously in the history??? It might be a case of resolution as the downtimes have only been 15seconds here , 50 seconds there, 25 seconds. Here are the screen shots to show this:
thanks
Geoff :-)
<http://www.fujixerox.com.au/> Geoff Swavley Infrastructure Specialist Business Services
Fuji Xerox Australia Pty Limited Level 1, 101 Waterloo Road MACQUARIE PARK NSW 2113 AUSTRALIA
Phone Fax email web (02) 9856 5468 (02) 9856 5003 Geoff.Swavley at aus.fujixerox.com <mailto:Geoff.Swavley at aus.fujixerox.com>
www.FujiXerox.com.au <http://www.fujixerox.com.au/>
This email (including any attachments) is confidential and may contain personal information within the Privacy Act 1988 (Cth). Fuji Xerox Australia make no warranties that it is free of viruses or has not been subject to unauthorised interference. If you have received it in error, please understand that confidentiality is not waived, please inform the sender by reply email, and delete it (and all copies) from your system.
Am Mittwoch, 4. Juli 2007 02:11 schrieb Geoff Swavley:
Hi All,
We're using Hobbit to pretty much monitor most things - and it works fine. One of our sections likes to keep track of the availablility of their web page and they have been using hobbit for this and are happy with what it gives them, except for an anomally from last month. When the availability report is run for last month I get a green diamond (presuming this to mean that it's 100%). We know it's not 100% by simply clicking on the http diamond and performing a history of the service. Why doesn't the monthly report tell us what is obviously in the history??? It might be a case of resolution as the downtimes have only been 15seconds here , 50 seconds there, 25 seconds. Here are the screen shots to show this:
within this 4 weeks (2419200 sec) there are 115sec unavailabillity (the second screenshot; do you know why?). This results in 99.995% availabilty, and if you show this value with 2 digits you get 100.00% (a very good value!).
thanks
Geoff :-)
<http://www.fujixerox.com.au/> Geoff Swavley Infrastructure Specialist Business Services
Fuji Xerox Australia Pty Limited Level 1, 101 Waterloo Road MACQUARIE PARK NSW 2113 AUSTRALIA
Phone Fax email web (02) 9856 5468 (02) 9856 5003 Geoff.Swavley at aus.fujixerox.com <mailto:Geoff.Swavley at aus.fujixerox.com>
www.FujiXerox.com.au <http://www.fujixerox.com.au/>
This email (including any attachments) is confidential and may contain personal information within the Privacy Act 1988 (Cth). Fuji Xerox Australia make no warranties that it is free of viruses or has not been subject to unauthorised interference. If you have received it in error, please understand that confidentiality is not waived, please inform the sender by reply email, and delete it (and all copies) from your system.
Good Luck
Rolf
On Wed, Jul 04, 2007 at 10:11:43AM +1000, Geoff Swavley wrote:
When the availability report is run for last month I get a green diamond (presuming this to mean that it's 100%).
green actually means 99,995% available.
I don't recall where this number comes from, but I believe it was adopted from the way the old Big Brother reports were built.
You can change the 99,995% setting by putting BBREPGREEN=100 in hobbitserver.cfg
There's also a debugging utility in the Hobbit sources that can help track down such problems. When you build Hobbit, a small utility is built in hobbit-4.2.0/lib/availability - this analyzes the history log in the same way that the reporting module does. So you can run it like this:
./lib/availability ~hobbit/data/hist/myserver.http
date +%s --date="1 Jun 2007"
`date +%s --date="1 Jul 2007"
The output is rather detailed, but buried inside you'll find the analysis of how many seconds each color was. It looks like this:
2007-07-04 09:48:54 Duration for color 0: 6610128
2007-07-04 09:48:54 Duration for color 1: 0
2007-07-04 09:48:54 Duration for color 2: 0
2007-07-04 09:48:54 Duration for color 3: 330548
2007-07-04 09:48:54 Duration for color 4: 0
2007-07-04 09:48:54 Duration for color 5: 6853
2007-07-04 09:48:54 Color 0: Count=31, pct=95.14
2007-07-04 09:48:54 Color 1: Count=0, pct=0.00
2007-07-04 09:48:54 Color 2: Count=0, pct=0.00
2007-07-04 09:48:54 Color 3: Count=5, pct=4.76
2007-07-04 09:48:54 Color 4: Count=0, pct=0.00
2007-07-04 09:48:54 Color 5: Count=26, pct=0.10
2007-07-04 09:48:54 Availability: 99.90, color =4Color 5 is red, 4 is yellow, 3 is purple, 2 is blue, 1 is clear, 0 is green.
Regards, Henrik
On Wed, Jul 04, 2007 at 10:00:28AM +0200, Henrik Stoerner wrote:
On Wed, Jul 04, 2007 at 10:11:43AM +1000, Geoff Swavley wrote:
When the availability report is run for last month I get a green diamond (presuming this to mean that it's 100%).
green actually means 99,995% available.
BTW - the history log you showed in the screenshot has 128 seconds of outage during June.
The green level of 99,995 means you can have (1-0,99995)*60*60*24*30 = 129,6 seconds outage and remain green.
So you just managed to squeak past the 0,005% limit.
Regards, Henrik
participants (3)
-
Geoff.Swavley＠aus.fujixerox.com
-
henrik＠hswn.dk
-
rolf.masfelder＠nector.de