Indicators used in the Business Services view
Indicators are computed metrics. They provide an indication of how a system is performing from the capacity and forecasting perspective. They are derived information and not measurements. With indicators, you can get additional insight into the status of the managed entity.
BMC Helix Continuous Optimization produces indicators on Risk, Usage, and Days to saturation for each service pool that you have defined:
- A Risk indicator counts any indication that CPU, memory, or storage resource of server in a service pool is either already saturated or will soon be experiencing capacity contention. If you see such an indication for a service pool, you would like to pay attention to the server to find out whether there is a risk to be addressed.
The risk indicator is a score value ranging from 1 to 100, higher being worse. The score is computed by considering risks based on CPU, memory, and storage risk scores of the contained servers. - A Usage indicator counts the level of usage per resource, so that you can track which service pools have consumed the excess capacity. The usage score is computed by aggregating usage based on CPU, memory, and storage usage scores of the contained servers.
- A Days to saturation indicator indicates the estimated number of days before the CPU, memory, and storage resources achieve the configured threshold.
For Kubernetes, the equivalent to a service pool is a deployment. The Risk, Usage, and Days to saturation indicators for each deployment is calculated in a similar way as indicators for service pools, except the indicator values of contained pods are considered for a deployment.
For each business service or application, the indicators values are calculated based on the indicator values of contained service pools or deployments. The last 30 days of data is considered to calculate the indicator values. For more information about indicators, see Indicators.
Kubernetes pods and the servers of the following technologies are supported: VMware, AWS, Azure, Google Cloud, IBM Cloud AIX, Solaris, HP-UX, Hyper-V, KVM, Xenserver, Standalone systems.
| Indicator | Resource | Displayed on | Description |
|---|---|---|---|
Risk (IND_RISK_SCORE) | |||
| Risk (Business service) | Risk pie chart, Business Services summary table | Indicates the overall risk of the business service, calculated by taking the maximum of the risk values of the contained applications. If applications are not available, risk values of service pools are considered. For example, if the business service contains four applications, then the highest risk score out of these four is used as the risk score for the business service. | |
| Risk (Application) | Business Service summary table | Indicates the overall risk of the application, calculated by taking the maximum of the risk values of the contained service pools. | |
Risk (Service pool) | Risk | Business Services summary table, Summary tab in the Service Pool Details page | Indicates the overall risk of the service pool, calculated by taking the highest risk score of CPU, Memory, Storage resources of the service pool. |
| CPU | Summary tab in the Service Pool Details page | Maximum of the CPU risk scores of the contained servers in the service pool. CPU risk score of the contained servers are computed using key indicators such CPU days to saturation and CPU utilization. | |
| Memory1 | Summary tab in the Service Pool Details page | Maximum of the Memory risk scores of the contained servers in the service pool. Memory risk score of the contained servers are computed using key indicators such as memory days to saturation and memory utilization. | |
| Storage | Summary tab in the Service Pool Details page | Maximum of the Storage risk scores of the contained servers. Storage risk score of the contained servers are computed using key indicators such as storage days to saturation and storage utilization. | |
Risk (Deployment) | Risk | Business Services summary table, Summary tab in the Deployment Details page | Indicates the overall risk of the deployment, calculated by taking the highest risk score of CPU and Memory resources of the deployment. |
| CPU | Summary tab in the Deployment Details page | Maximum of the CPU risk scores of the contained pods in the deployment. CPU risk score of the contained pods are computed using key indicators such CPU days to saturation and CPU utilization. | |
| Memory | Summary tab in the Deployment Details page | Maximum of the Memory risk scores of the contained pods in the deployment. Memory risk score of the contained pods are computed using key indicators such as memory days to saturation and memory utilization. | |
| Risk (Server) | Risk | Contained Elements tab in the Service Pool Details page | Indicates the overall risk of the server, calculated by taking the maximum of the usage of CPU, Memory, Storage resources of the server. |
| CPU | Contained Elements tab in the Service Pool Details page | CPU risk score of the server. | |
| Memory1 | Contained Elements tab in the Service Pool Details page | Memory risk score of the server. | |
| Storage | Contained Elements tab in the Service Pool Details page | Storage risk score of the server. | |
| Risk (Pod) | Risk | Pods tab in the Deployment Details page | Indicates the overall risk of the pod, calculated by taking the maximum of the usage of CPU and Memory resources of the server. |
| CPU | Pods tab in the Deployment Details page | CPU risk score of the pod. | |
| Memory | Pods tab in the Deployment Details page | Memory risk score of the pod. | |
Usage (IND_USAGE_SCORE) | |||
Usage (Business service) | Usage histogram, Business Services summary table | Indicates the overall usage of the business service, calculated by taking the average of the usage values of the contained applications. If applications are not available, usage values of service pools are considered. | |
| Usage (Application) | Business Services summary table | Indicates the overall usage of the application, calculated by taking the average of the usage values of the contained service pools. | |
Usage (Service pool) | Usage | Business Services summary table, Summary tab in the Service Pool Details page | Indicates the overall usage of the service pool, calculated by taking the average of the usage of CPU, Memory, Storage resources of the service pool. |
| CPU | Summary tab in the Service Pool Details page | Average of the CPU usage of the contained servers. | |
| Memory1 | Summary tab in the Service Pool Details page | Average of the memory usage of the contained servers. | |
| Storage | Summary tab in the Service Pool Details page | Average of the storage usage of the contained servers. | |
Usage (Deployment) | Usage | Business Services summary table, Summary tab in the Deployment Details page | Indicates the overall usage of the deployment, calculated by taking the average of the usage of CPU and Memory resources of the deployment. |
| CPU | Summary tab in the Deployment Details page | Average of the CPU usage of the contained pods. | |
| Memory | Summary tab in the Deployment Details page | Average of the memory usage of the contained pods. | |
| Usage (Server) | Usage | Contained Elements tab in the Service Pool Details page | Indicates the overall usage of the server, calculated by taking the average of the usage of CPU, Memory, Storage resources of the server. |
| CPU | Contained Elements tab in the Service Pool Details page | CPU usage score of the server. | |
| Memory1 | Contained Elements tab in the Service Pool Details page | Memory usage score of the server. | |
| Storage | Contained Elements tab in the Service Pool Details page | Storage usage score of the server. | |
| Usage (Pod) | Usage | Pods tab in the Deployment Details page | Indicates the overall usage of the pod, calculated by taking the average of the usage of CPU and Memory resources of the pod. |
| CPU | Pods tab in the Deployment Details page | CPU usage score of the pod. | |
| Memory | Pods tab in the Deployment Details page | Memory usage score of the pod. | |
Days to saturation (IND_DAYS_TO_SATURATION) | |||
Days to saturation (Business service) | Saturation by Service Importance bubble chart, Business Services summary table | Indicates the days to saturation value for the business service, calculated by taking the minimum of the days to saturation values of the contained applications. If applications are not available, days to saturation values of service pools are considered. For example, if the business service contains four applications, then the lowest days to saturation value out of these four is used as the days to saturation value for the business service. | |
Days to saturation (Application) | Business Services summary table | Indicates the days to saturation value for the application, calculated by taking the minimum of the days to saturation values of the contained service pools. | |
Days to saturation (Service pool/deployment) | NA | Indicates the days to saturation of the service pool or deployment. It is the estimated number of days before the CPU, memory, and storage resources achieve the configured threshold. | |
| CPU | NA | Minimum of the CPU days to saturation indicators of the contained servers or pods | |
| Memory | NA | Minimum of the memory days to saturation indicators of the contained servers or pods | |
| Storage | NA | Minimum of the storage days to saturation indicators of the contained servers or pods. | |
1 For VMware, AWS, Azure, Google Cloud, Hyper-V, KVM, and Xenserver technologies, if the virtual node (with namespace as opt:vn) data is available, the memory score is computed based on the virtual node memory data. Otherwise, it is computed based on the memory of the virtual machine.
Click here to view the PDF that includes the detailed computation of the indicators used in the Business Service view.
Comments
Log in or register to comment.