[Orca-users] uptime stats

[Sean O'Neill]

At 12:41 PM 2/4/2003 -0600, Sean O'Neill wrote:
>At 11:54 AM 2/4/2003 -0600, Sean O'Neill wrote:
>>At 11:03 AM 2/4/2003 -0600, Sean O'Neill wrote:
>>>At 11:50 AM 2/4/2003 -0500, mtb wrote:
>>>>Thanks for the reply, Sean.
>>>>
>>>>Orcallator already collects uptime... it's the third field.  It's a 
>>>>number... looks like this:
>>>>
>>>>timestamp  locltime   uptime
>>>>1044334804 00:00:04 15169896
>>>>
>>>>How do I interpret that number?  I don't want to get into running some 
>>>>external job out of cron if orcallator already has the data.
>>>
>>>Ahhh, learn something new every day :)
>>>
>>>Its simply the number of seconds the box has been up since the last reboot.
>>>
>>>And now that I think about it - My epoche seconds thought is 
>>>nuts.  Epoche seconds gives a specific point in time - not duration - in 
>>>this case anyway.
>>>
>>>In your .cfg file, you could do some RRD math and convert seconds to 
>>>days and graph that number.
>>
>>This is pretty easy now that I've looked at it.  I added this to my 
>>orcallator.cfg file just below the "System State" block.
>>
>>plot {
>>title                   %g Uptime
>>source                  orcallator
>>data                    uptime / 86400
>>line_type               area
>>legend                  Uptime
>>y_legend                Days
>>data_min                0
>>}
>>
>>Rerunning Orca on this now.  Let you know how it works.
>
>Works great ... check it out:
>
>http://chivas.oneill.dhs.org/orca/o_gauge_uptime_per_86400-all.html

Blair, you want this in subversion ?  I think it would be nice to have by 
default.


--
........................................................
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill