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.

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.

 

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