Re: Process data in overview list

[Jan-Henrik Haukeland]

Christian Hopp <address@hidden> writes:

> Memory works fine... but cpu has a problem... I measure the cpu% by
> substracting two tick counts.  The more you wait the better the
> measurement.  That means I have to measure twice in "monit status".
> Hence, we have to wait for n secons before we get the result.
> 
> Otherwise we have to get the data from the server.  But that would
> mean that we have to connect to it.  Ideas(?)...  maybe the status
> output is generated by the server and we connect to the web interface
> and get a text/plain file instead of the usual text/html.  It would be
> like the stop/start/restart commands on the cli.

Yes, the best thing is probably to connect to the server as with the
start/stop commands. If you cannot connect to the server because it
was not started with http support the next best thing is not to show
the cpu info, maybe with info on why not, for instance "Cannot show
cpu info because the monit daemon was not started with http support"

-- 
Jan-Henrik Haukeland