Summary:ASTERISK-09347: Cpusage
Reporter:Phillip (killfill)Labels:
Date Opened:2007-04-28 15:23:14Date Closed:2007-05-16 18:34:39
Versions:Frequency of
Environment:Attachments:( 0) cpusage.diff

Im not sure if it really asterisk-gui's work to monitor the hardware where its running. There are big tool that can do this, and i think its a totally different matter from asterisk*. The time spent in this, could be maybe better applied in asterisk things :) but i know, graphs is a funny thing to work on.. ;) Or maybe we could graph calls instead of OS/hardware stuff :P

Anyway, -gui could use cpusage: http://lists.digium.com/pipermail/asterisk-gui/2007-April/000423.html

i guess the graph parser will need some change.. :P

Comments:By: Brandon Kruse (bkruse) 2007-05-03 17:05:00

Thanks again for the contribution.

But I am on the verge of adding hardware specific calculations and statistics in manager as is.

The bash script was just a proof of concept to see how the community would react.

Thanks though!

By: Phillip (killfill) 2007-05-03 19:23:57

yup.. manager is the one that should have this info...

take this as a simple reaction :P


(just close this)

By: Brandon Kruse (bkruse) 2007-05-03 22:41:08

Ha, No Problem.

Your the only one to try to contribute so far, so I appreciated It ;]


By: Pari Nannapaneni (pari) 2007-05-16 18:34:39


We appreciate for submitting the patch - but the GUI's
aim is to run on as many platforms as possible with already
available tools. Using your 'cpu usage' tool in the GUI means
that we have spend some time porting it to the digium appliance and
other *nix platforms and would be yet another tool that the gui needs
to run. That's why we are trying to do most of the stuff in
bash, or javascript or in asterisk.

But as you said - we will be soon working on graphs for active calls/queues etc.