Re: How can i monitor CPU like this? (137 Views)
Reply
Valued Contributor
thaolv
Posts: 113
Registered: ‎05-07-2013
Message 1 of 2 (149 Views)
Accepted Solution

How can i monitor CPU like this?

[ Edited ]

Hi,

 

I need to divide CPU Utilization policy into 3 stages:
Everyday: - from 8h00 to 15h00: specify a threshold

                    - from 15h00 to 17h00: specify a threshold

                    - from 17h00 to 8h00: specify a threshold

I need to control threshold for myself in each stage.

 

Thank you

Please use plain text.
HP Expert
Ramkumar Devanathan
Posts: 1,558
Registered: ‎07-31-2002
Message 2 of 2 (137 Views)

Re: How can i monitor CPU like this?

Hi, if you are using the SISPI, then you would know that it is possible to set thresholds outside of the policy, using xpl config.

 

So, you need to set / change the thresholds at different times of day.

 

to change the thresholds you would call ovconfchg command.

to do changes per a schedule, you could use a schedule policy and read from a config file containing the change time and new set of thresholds. sample config file below assuming you wish to change only the cpu usage threshold. you can be creative and add some more threshold values for 'load average' too.

 

#config file

# time_of_day  thresholds_for_cpu_usage

0800-1459  t1,t2,t3,t4

1500-1659  t5,t6,t7,t8

1700-0759  t9,t10,t11,t12

 

#EoF

 

the schedule policy would check current system time and at 0800 run the following commands -

ovconfchg -ns eaagt -set CpuUsageCriticalThreshold t1

ovconfchg -ns eaagt -set CpuUsageMajorThreshold t2

ovconfchg -ns eaagt -set CpuUsageMinorThreshold t3

ovconfchg -ns eaagt -set CpuUsageWarningThreshold t4

 

and so on.. optimization can be done to avoid re-implementing the same thresholds every interval - change only when needed.

 

If you are doing this with your own OM measurement threshold policy, then you can handle the threshold change using scripting - but the thresholds will remain externally inaccessible.

 

If you are using a simple monitor policy (like OMU 8x style) then you would need 3 sets of policies with differing thresholds set internally, and then you can disable/enable the ones required/not required using a different scheduler policy.

 

Let me know if you need more info/details.

 

HTH

- ramd.

HP Software Rocks!
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation