Redpeaks V7.0
Trouble shooting
Monitors Guide
Trouble shooting
Monitors Guide
Add this page to your book
Remove this page from your book Monitors the CPU usage of HANA database at the instance and service levels.
CPU utilization is computed at different levels:
| Auto clear | If set, the generated alarms will be automatically cleared from the console if the alarm condition is not fulfilled anymore |
|---|
| Parameter | Description |
|---|---|
| Active | If checked, the rule is enabled and will be processed |
| Host | Can be used to restrict the monitoring to a given host (multi instance case). A star (‘*’) will match any host |
| Service | Defines which service is monitored. A star (‘*’) will match any service, and therefore, it will calculate the combined usage of all services. Otherwise, it is the usage of the specified service that will be calculated |
| Max current CPU (%) | The alarm threshold for the current CPU usage |
| Max CPU over period (%) | The alarm threshold of the CPU usage over the period set in the “Period” field |
| Period (min) | The period of time used to calculate the CPU usage |
| Severity | Defines the level of severity of the alarm that will be generated if one of the thresholds is reached |
| Alarm tag | You can define some text to use as a prefix of the alarm message generated by the current rule |
| Alarm | Defines if an alarm has to be generated for the given rule |
| Metric | Defines if a metric has to be generated for the given rule |
| metricId | metricUnit | metricTarget | metricDescription |
|---|---|---|---|
| DB_CPU_UTILIZATION | Percent | HOST | Sends the CPU utilization per node |
| DB_CPU_UTILIZATION_PER_SERVICE | Percent | HOST - SERVICE | Sends the CPU utilization per service |
| DB_CPU_UTILIZATION_SMOOTHED_PER_SERVICE | Percent | HOST - SERVICE | Sends the CPU utilization smoothed over a period, per service |