Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on November 3, 2025. We recommend that you use PATROL for Linux, PATROL for AIX, or PATROL for Solaris to monitor operating systems.

% Utilization Out of Cpu Cap (PROJCpuCapUtilPerc)


This parameter reports the percentage of CPU cap that is project is currently utilizing.
 Like zones, a project can have a CPU cap value set in terms of number of processors, to limit CPU utilization by the project. This ensures that the CPU utilization does not exceed the cap even though more processors are available. This makes the PROJCpuUtil parameter for CPU utilization inadequate.

For example, assume that the project has 5 physical processors available, but has CPU cap set to 150 (that is, 1.5 physical processors). Even though it has 5 processors available, it can not use more than 1.5 processors. Thus, when the project uses 1.5 processors, the CPU utilization for the project as reported by the PROJCpuUtil  parameter is 30% (calculated as 1.5 x 100 / 5). However, since the project has consumed the maximum processors that it is entitled to use, that is 1.5 processors, it has fully utilized the CPU cap.

The PROJCpuCapUtilPerc parameter represents the very same thing; it reports the amount of CPU cap that has been consumed by the project. In the above example, this parameter will report a value of 100%.
 This parameter is available only when the project has been provided with the CPU cap. The CPU cap for a project is controlled by the system resource control, project.cpu-cap. This parameter is deactivated if the corresponding CPU cap value is not provided for the respective project.

Default parameter attributes

Attribute

Default value

Application class

PROJECT

Command type

not applicable

Platform

Solaris 10 and above

Icon style

graph

Unit

percentage

Border range

0-100

Alarm1 range

90-95
WARNING: after two consecutive hits in the range

Alarm2 range

95-100
ALARM: after two consecutive hits in the range

Scheduling (poll time)

Iinherits poll time of collector

Active at installation

yes

Parameter type

consumer

Value set by

BMC ProactiveNet Performance Management properties

Property

Default value

Monitor type

Solaris Project

Key Performance Indicator

No

Monitor for abnormalities

Yes

Graph by default

No

Availability

No

Response time

No

Normal distribution

Yes

Statistical

Yes

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*