Collecting data for business services, applications, and service pools

The Analyzing business services provides the consolidated summary of all business services in your infrastructure. The data displayed in the Business Service view consists of a service model and metrics to measure the system performance. The service model is the mapping between business services, applications (optional), and the systems in your cloud and on premises environments. For analyzing and managing the capacity of your business services, applications, and systems, you must first import their data in the BMC Helix Continuous Optimization database. This data is then processed and displayed in the Business Services view where you can monitor your systems to identify capacity-related risks and issues. 

Service pools in cloud and on premises

For cloud and on premises, you can configure your systems to add one more layer in the service model called service pools. You need to explicitly create the service pools.

Deployments in Kubernetes

Deployments in Kubernetes are conceptually similar to service pools, therefore, deployments are used in the service model and view as is. You need not create service pools for Kubernetes as deployments are directly available when you import the Kubernetes data.

Step 1: Prepare your systems in the on cloud and on premises environments.

Complete these tasks to prepare your on cloud and on premises systems for data collection:

Resource typeTasksDetails

Virtual machine instances provisioned in the public clouds, such as AWS, Azure, Google Cloud Platform, and IBM Cloud.

Access the cloud provider console and add tags to the virtual machine instances. These tags are used by the ETLs to create a hierarchy of business services, applications, service pools, and underlying systems in the Workspace. You can use the following default tag types:

  • Service: To create a business service. For example, Service=HR creates a business service named HR.
  • AppTier: To create a service pool. For example, AppTier=webserver creates a service pool named webserver_Pool.
    You can modify this tag type. For more information, see Configuring the business services view settings.

AWS: Tagging your Amazon EC2 resources Open link

Azure: Use tags to organize your Azure resources Open link

Google Cloud: Use labels to organize your Google Cloud resources Open link

IBM Cloud: Use tags to organize your IBM Cloud resources Open link

Virtual machines and physical systems in your on-premises environment.

Use any of the following methods to create relationships between business services, applications (optional), and computer systems.

  • Organize your systems in the BMC Atrium CMDB. The CMDB creates the mapping between business services, applications (optional), and computer systems.
  • Organize your systems in the BMC Discovery and add manual groups.
  • Define the relationships between business services, applications (optional), and systems in a CSV file.

To define names for service pools, configure and run the Generic - Tag CSV file parser ETL to add the AppTier (or the one that you configured) tag type to the systems in your on premises environment.

  • BMC Atrium CMDB documentation Open link
  • Generic - Tag CSV file parser ETL
  • BMC Discovery documentation Open link


If you are using BMC Helix Discovery, then you can use the business service models from the common services that are defined in BMC Helix Discovery. For more information, see Integrating with BMC Helix Discovery.

Deployments in your Kubernetes environment

Use the following method to create relationships between business services, applications (optional), and deployments.

  • Define the relationships between business services, applications (optional), and systems in a CSV file.

Step 2: Configure and run the ETLs to import data.

Configure and run the out-of-the-box ETLs to import infrastructure data and view the hierarchy.

Import data fromETLs to be run

Cloud systems

Depending on your cloud platform, configure and run the following ETLs:

When you run the ETLs, the hierarchy and infrastructure data is imported in the BMC Helix Continuous Optimization database.

On-premises systems

Configure and run the out-of-the-box ETLs to collect the performance data of your systems.

Kubernetes resources

Step 3: Set the tags for business services
  1. Navigate to Workspace > Domains, Services & Applications.
  2. In the navigation panel, locate the desired business service and click its name to display the details page in the working area.
  3. In the Tags panel, click Add tag and enter the name of the new tag.
  4. Select the tag type, for example, Importance. 

    • A tag name and tag type cannot contain the following special characters: 
      [ ] , : ; " | * & \ / ? $ £ ( ) { } ^ ~
    • A tag type must not exceed 50 characters.
    • A tag name (value) must not exceed 4000 characters.
  5. Click Add Tag.

(Optional) Step 4: Set the tags for business drivers

By default, BMC Helix Continuous Optimization calculates the supported growth for business drivers against the business service based on the best-suited metric of that business driver. If you want to explicitly select a different metric to be used to compute the supported growth, you can set the tag by specifying the resource name of that metric. 

  1. Navigate to Workspace > Domains, Services & Applications.
  2. In the navigation panel, locate the required business driver and click its name to display the details page in the working area.
  3. In the Tags panel, click Add tag and enter the name of the new tag.
  4. Select the tag type as Supported Growth Metric and select the resource name of the required metric.

    • A tag name and tag type cannot contain the following special characters: 
      [ ] , : ; " | * & \ / ? $ £ ( ) { } ^ ~
    • A tag type must not exceed 50 characters.
    • A tag name (value) must not exceed 4000 characters.
  5. Click Add Tag.

(Not required for Kubernetes) Step 5: Configure the settings for service pools.

You can configure the settings to specify the domains for which you want to create service pools. When you save these settings, the service pools are created and indicators are computed.

For more information, see Configuring the business services view settings.

Step 6: View the hierarchy and verify the collected data.

In the Workspace, verify the hierarchy and the collected metrics:

  • Business services are organized under a domain.
  • (optional) Applications are organized under business services.
  • Deployments and pods are organized under the respective domain for Kubernetes.
  • Service pools are created for the selected domains and displayed in the Service Pools folder, and the systems are organized under the service pools.

The following table explains how the service pool naming changes based on the tags.

ScenarioOrganization in your environmentHierarchy displayed in the WorkspaceExample

You have tagged all the systems.


Business services and systems

Business services > service pools > systems

(The service pools are placed under the business services and named based on the tag values.)

The following tag is added to your systems:

AppTier=WEB_SERVER

The service pool named WEB_SERVER_Pool is created and all the systems are placed under this service pool:

Business services, applications, and systems

Business services > applications > service pools > systems

(The service pools are placed under the applications and named based on the tag values.)

The AppTier tag with "DB" value is added to some systems and with the "WEB" value to the remaining systems. The following hierarchy is displayed:

You have not tagged any of the systems or selected the tag type in the Settings pageBusiness services and systems

Business services > service pools > systems

(The service pools are placed under the business services and named based on the corresponding business service names.)

Business services, applications, and systems

Business services > applications > service pools > systems

(The service pools are placed under the applications and named based on the corresponding application names.)

You have tagged some of the systems.

Business services and systems

Business services > service pools > systems

(The service pools are placed under the business services. The service pools for the tagged systems are named as per the tags. The service pools for untagged systems are named based on the corresponding business service names.)

The following tag is added to some of the systems:

AppTier=WEB_SERVER

The systems with this tag are placed under the WEB_SERVER_Pool folder and the remaining untagged system is placed under the service pool that is named as per the business service.

Business services, applications, and systems

Business services > applications > service pools > systems

(The service pools are placed under the applications. The service pools for the tagged systems are named as per the tags. The service pools for untagged systems are named based on the corresponding application names.)

The AppTier tag with the "DB" value is added to some systems and with the "WEB" value to other systems. This tag is not added to the remaining systems. The following hierarchy is displayed:

.

Was this page helpful? Yes No Submitting... Thank you

Comments