My experience too. A lot of monitoring is done with dedicated servers in
mind. So CPU resources are allowed to be wasted and one doesn't care
about keeping the machine active. The same scripts are then used in
virtual environments and then they wonder why they get the wrong
numbers, why there are performance problems (or seemds to be performance
problems), etc. Obviously the CPU load, IO and such depend on how often
you run the script.

Look at what you need to monitor. CPU numbers within the guest can be
wrong. We have two guests hardlimitted on an absolute share of 11%.
Every day they create alerts for high CPU loads within the guest. While
they only are limitted in VM because of the share. So monitoring in the
guest can give you alerts for the wrong event. If you want to monitor
the guest for high user CPU chances are the guest is also running high
CPU load in VM too. 

If you use the appldata and/or mon_procd services in linux you can
monitor also usercpu from VM. The CP MONITOR holds the numbers, use a
rexx to obtain them.

Regards, Berry.

-----Original Message-----
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Shane
Sent: donderdag 9 december 2010 12:22
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Need a little help with a Linux script

On Thu, 9 Dec 2010 09:57:55 +0100
Agblad Tore wrote:

> I would say: don't use script for monitoring cpu.
> You may not get the correct cpu figures from inside the Linux and 
> these cmds in scripts consumes huge cpu and I/O !!

I can't see where parsing the output from mpstat would universally
qualify for this admonition.
Your bad experience is yours, not everyone elses.

> Do it in z/VM and a nice Rexx instead, much better !

This may well be true for something like overall CPU usage of the entire
guest - bit hard to determine userspace usage from the hipervisor
though. Probably also presumes the availability of a monitor product of
some sort on z/VM.

Shane ...

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to