Collecting data for business services, applications, and service pools

The service model contains the mapping between business services, applications, 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 TrueSight Capacity Optimization database. This data is processed and displayed in the views where you can monitor your systems to identify capacity-related risks and issues. The data consists of a service model and metrics to measure the system performance. 

You can configure your systems to add one more layer in the service model called service pools and analyze the capacity at the service pool level. For information about service pools, see Business services, applications, and service pools

To collect data for business services, applications, and service pools, do the following tasks:

  1. Prepare your systems in the on cloud and on premises environments.
  2. Configure and run the ETLs to import data.
  3. Configure the settings for creating service pools.
  4. View the hierarchy and verify the collected 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, and Google Cloud Platform.

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 tags:

  • 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

Azure: Use tags to organize your Azure resources

Google Cloud: Use labels to organize your Google Cloud resources

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
  • Generic - Tag CSV file parser ETL
  • BMC Discovery documentation

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 of business services, applications (optional), and computer systems.

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 TrueSight Capacity Optimization database.

On premises systems

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

Step 3: 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 4: 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.
  • 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