Command Central 10.3 | Command Central Developer Reference | Configuring Command Central and Platform Manager | Run-time Monitoring States for OSGI-CCE and OSGI-SPM
 
Run-time Monitoring States for OSGI-CCE and OSGI-SPM
When you run sagcc get monitoring state, the OSGI-CCE and OSGI-SPM run-time components return details about key performance indicators (KPIs) used for monitoring. Take corrective actions when the KPI threshold approaches critical values. The following table lists the KPIs that are used and describes what they monitor.
KPI
Use to monitor...
JVM CPU Load
How much CPU the JVM uses.
KPI values:
*Marginal is 80% CPU usage.
*Critical is 95% CPU usage.
*Maximum is 100% CPU usage.
KPI limitations:
*supported only when running Java 7 or higher
*not reported when running on HP-UX
JVM Memory
How much JVM memory the run-time component uses.
KPI values:
*Marginal is calculates as follows:
MAX(Maximum*80%, Maximum-100)
A marginal value is when only 20% of the JVM memory is free or less than 100MB of JVM memory is available.
*Critical is calculated as follows:
MAX(Maximum*95%, Maximum-50)
A critical value is when only 5% of the JVM memory is free or less than 50MB of JVM memory is available.
*Maximum is the amount of memory allocated to the JVM.
KPI limitation: the KPI value might be incorrect when running in a 32-bit operating system.
JVM Threads
The number of JVM threads that the run-time component uses.
KPI values:
*Marginal and Critical are the current number of the allocated JVM threads plus one thread: current+1.
*Maximum is the maximum allocated JVM threads plus one thread: MAX+1