Re: cpu usage threshold (360 Views)
Reply
Valued Contributor
Sridhara
Posts: 287
Registered: ‎04-26-2006
Message 1 of 4 (384 Views)
Accepted Solution

cpu usage threshold

Hi,

 

In CPU/Memory usage monitoring threshold, by default, critical is 65535. Can some body explain what 65535 is.

Regards,
Sridhara.
Please use plain text.
HP Expert
Carlos_Pinto
Posts: 280
Registered: ‎06-01-2012
Message 2 of 4 (372 Views)

Re: cpu usage threshold

Hello,

 

Currently the memory= value (in procthreshold line) is limited to 65535.

 

Please see the below document with further information:

 

http://support.openview.hp.com/selfsolve/document/LID/QCCR1A123638

 

 

Hope this information helps.

 

Thanks and Regards,

Carlos Pinto

 

HP Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution

If you liked it I would appreciate KUDOs

Please use plain text.
Valued Contributor
Sridhara
Posts: 287
Registered: ‎04-26-2006
Message 3 of 4 (362 Views)

Re: cpu usage threshold

HI Carlos,

 

 

thanks foe your info. but can you tell me is it whether 65535 indicates threshold of 100% or something else

Regards,
Sridhara.
Please use plain text.
HP Expert
Ramkumar Devanathan
Posts: 1,623
Registered: ‎07-31-2002
Message 4 of 4 (360 Views)

Re: cpu usage threshold

Sridhara,

 

we have a convention in the system monitoring SPI not to send critical alerts. We decided early on during the development phase that real critical alerts are reserved for higher level app failures, crucial failures and the like - not for common cpu and memory problems.

 

So in SISPI we do not ship policies with critical rule settings that send out critical severity alerts any more - by default.

That's the reason we have the critical alerting rule, but we have set the threshold to ridiculously high values that the rule will not fire.

 

However this might bring up the question that a real problem scenario is lost without alerts being sent - Don't worry, this is not missed.

Here's how the policy is designed, if a policy is generally designed to send out a critical, major, minor alert at 95, 90, 80% utilisation respectively, we now set this in a shifted mode - the major alert is sent at 95%, the minor alert is sent at 90% and so on.

So when you receive a major alert from the SISPI this is in fact something important to look at - but it does not look so bad from the high-level KPIs which in turn might get affected by the alert.

 

short answer: 65535 is a ridiculous threshold, set on purpose.

 

Hope this helps.

PS: in the Infrastructure SPI concepts guide - see chapter 5 which explains this as a dialog between a newbie and an expert.

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