Configuring and managing thresholds for metrics and indicators
You can add, edit, or delete a threshold only if your user role is assigned to the optimizer_rule_edit permission. For more information, see Default-user-roles-and-permissions.
When you add or modify the thresholds, it affects various functionalities of BMC Helix Continuous Optimization. Some functionalities use only the warning thresholds, while others use both thresholds. For details, see How-optimizer-thresholds-affect-other-functionalities-of-BMC-Helix-Continuous-Management.
To configure and manage metric thresholds
- To view metric thresholds
- To add a metric threshold
- To edit a metric threshold
- To delete a metric threshold
To view metric thresholds
Click Administration > OPTIMIZER > Thresholds. Ensure that the Metrics tab is selected.
All the metric thresholds are displayed in a table. Here are the column descriptions:
To add a metric threshold
- Click Administration > OPTIMIZER > Threshold. By default, the Metric thresholds page is displayed.
- Click Add Threshold.
- Specify the following details:
- Entity type: Select whether the thresholds must apply to all or specific systems or business drivers.
- If you select All entity types, then the scope of the metric threshold is set to be global.
- If you select specific system or business driver type, the scope depends on that specific entity type. The tags field is also enabled for configuration.
(Optional) Tags: Select the tag type and the tag value to further filter the systems or business drivers for which you want to apply the threshold. Depending on the specific system or business driver that you have selected in the previous field, the applicable tag types are displayed. Based on the selected tag type, the tag values are displayed.
If you have chosen Generic entity type and you intend to set thresholds on a Database Server entity, pick SERVER_TYPE in the Tags field and pick DATABASE as the tag value.If you have chosen Generic entity type and you intend to set thresholds on a Database Server entity, pick SERVER_TYPE in the Tags field and pick DATABASE as the tag value.
- Metric: Select the metric for which you want to add threshold values.
Value: Select whether you want to specify fixed values for good or warning thresholds or whether you want to base the thresholds on another metric.
- If you select Fixed value, specify a fixed Good Threshold and Warn Threshold, measured in Operations/second.
- If you select Based on limit metric, select a metric and specify a Good Threshold and Warn Threshold, measured in percentage of the limit metric.
- Entity type: Select whether the thresholds must apply to all or specific systems or business drivers.
- Click Save.
The threshold is added to the table on the Metric thresholds page.
To edit a metric threshold
- Click Administration > OPTIMIZER > Threshold. The Metric thresholds page is displayed by default.
- In the table on the page, for the threshold that you want to modify, click the Edit
icon.
- In the Edit threshold section of the page, modify the Good Threshold and Warn Threshold values.
- Click Save.
To delete a metric threshold
- Click Administration > OPTIMIZER > Threshold. The Metric thresholds page is displayed by default.
- In the table on the page, for the threshold that you want to delete, click the Delete
icon.
- Click Delete.
To configure indicator parameters and thresholds
Access the Indicators page by clicking Administration > OPTIMIZER > Thresholds > Indicators. The indicator parameters and thresholds are displayed.
To modify these values, scroll down to the bottom of the page and click Edit, and after completing the changes, click Save. You can neither add nor delete a parameter or threshold. When you modify any of the indicator thresholds, it might take up to a day to see the updated indicator values for affected systems.
The following table provides a list of the indicator parameters and thresholds, their default values, and the indicator that is impacted when their values change. For more information about indicators, see Indicators.
Indicator parameter or threshold | Default value | Impacted indicator |
---|---|---|
Days to saturation | ||
Minimum number of days needed to calculate trends | 5 days | Days to saturation (IND_DAYS_TO_SATURATION) |
Use long term data to compute indicators | No | |
Number of months of long term historical data | 3 months | |
Ignore already saturated resources | No | |
Use cluster size as max of last 7 days | No | |
Idle VMs | ||
CPU utilization threshold | 5 % | Days idle (IND_DAYS_IDLE)
|
Network rate threshold | 5 Mbytes/s | |
Disk I/O rate threshold | 5 Mbytes/s | |
Overallocated VMs and Forecasted Saturation for VMs | ||
vSphere VM Active Memory increase factor | 50 % | Memory Demand (IND_MEMORY_DEMAND) |
Virtualization Readiness | ||
CPU consumption metric mandatory | True | Virtualization Readiness Index (IND_VIRT_READINESS) |
CPU consumption threshold | 5 GHz | |
Memory consumption metric mandatory | True | |
Memory consumption threshold | 8 GB | |
Disk consumption metric mandatory | False | |
Disk consumption threshold | 7.5 Kbyte/s | |
Network consumption metric mandatory | False | |
Network consumption threshold | 1 Gbit/s | |
CPU/Memory/Storage Pressure | ||
CPU Pressure Indicator for VMware Clusters and Hosts | ||
CPU Ready threshold for VMs | 10% | CPU Pressure Index (IND_CPU_PRESSURE) |
Minimum VMs considered for CPU Ready impact | 10 | |
Composite Memory (Memory Pressure Indicator) for VMware Clusters, Hosts and Capacity Pools | ||
Ratio of consumed memory by active memory threshold | 6 |
|
Memory overcommitment threshold | 1.2 | |
Storage Pressure Index for VMware Clusters and Capacity Pools | ||
I/O latency threshold | 30 MILLIS | Storage Pressure Index (IND_STORAGE_PRESSURE) |
Minimum Datastores that can exceed I/O latency threshold | 10 | |
CPU Pressure Indicator for AIX PowerVM Hosts | ||
CPU Queue Length threshold for partitions | 4 | CPU Pressure Index (IND_CPU_PRESSURE) |
Minimum Partitions considered for CPU Queue Length impact | 5 | |
Memory Pressure Indicator for AIX PowerVM Hosts | ||
Memory page rate threshold for partitions | 64 bytes/s | Memory Pressure Index (IND_MEMORY_PRESSURE) |
Minimum Partitions considered for Memory page rate impact | 20 | |
Memory Pressure Indicator for Virtual Machines | ||
Minimum swap rate exceed count | 1 | Memory Pressure Index (IND_MEMORY_PRESSURE) |
Spare VMs | ||
Use Composite Memory Utilization indicator instead of Memory Utilization metric | True | Spare VMs (IND_SPARE_VM) |
Default VM CPU usage | 1 GHz | |
Default VM memory usage | 2 GB | |
Default VM storage usage | 16 GB |