Page tree

The Collection Profiles tab allows you to configure data collector templates that can simplify the process of data collection. A collection profile allows administrators to capture the input parameters necessary for creating a data collector and then reuse it for future configurations. You can create a collection profile by adding a new data collector or using an existing data collector. Once you have created the collection profile, you can associate it with the appropriate host. As soon as you associate the collection profile with the host, in a short period of time, data collectors are automatically added under the Data Collectors tab.

Note

Creation of collection profiles depends on the number of hosts. You can create one collection profile per host or many collection profiles per host. In a single server environment, where all the components of your application are deployed on the same server, you can create one collection profile with data collector templates for each of the components. After this is done, associate that collection profile with the single host.

Advantages of using a collection profile

A collection profile has the following advantages:

  • Reduces the amount of manual work and time for configuring data collectors.
  • Reduces errors introduced during manual configuration.
  • Ensures consistent collection configuration across respective environments.
  • Helps automate the collection configuration of hosts and allow it to be driven from the BMC ProactiveNet Performance Management (or the BMC PATROL KM for IT Data Analytics) configuration.

Use case for using a collection profile

Collection profiles can be useful in a scenario where you have multitier applications existing on multiple hosts. The following use case describes such a scenario:

Example

Base Scenario: Suppose you are an administrator responsible for collecting data. In this role, you will first identify the various hosts in your environment from which you want to collect data. Suppose that in your environment, you have two applications with two tiers and each tier lies on a different host.

Environment: Application A is made up of Apache Tomcat with an Oracle database on the back end (that resides on a separate host). Application B is made up of Apache Tomcat with a Microsoft SQL Server on the back end (that resides on a separate host). While Application A runs on both Windows and Linux, Application B runs on Windows only. Oracle runs on Linux, while Microsoft SQL Server runs on Windows. Multiple instances of Applications A and B are spread across multiple hosts.

Usage: As an administrator, you can proceed as follows:

  1. Identify the common profiles that exist across the various hosts supporting the two applications:
    • Oracle database log files on Linux
    • Microsoft SQL Server database log files on Windows
    • Apache Tomcat generic log files on Windows and Linux
    • Application-specific log files for Application A on Windows and Linux
    • Application-specific log files for Application B on Linux
  2. Identify the log file paths for each of the profiles identified in step 1. Navigate to Administration > Collection Profiles and configure a collection profile for a specific host, adding separate data collector templates for each of the profiles. While adding a data collector template, you can specify the input parameters required for the data collection, the tags, and the group access permissions that will be passed on to the data collector.
  3. Navigate to Administration > Hosts, and associate the collection profile with each of the hosts relevant to the various profiles.
  4. Within a short period of time, the data collectors for each of the profiles are automatically created and data collection starts.

Viewing and searching configured collection profiles

The Collection Profiles tab allows you to manage collection profiles. To access this tab, navigate to Administration > Collection Profiles. From here, you can perform the following actions:

ActionIconDescription
Add Collection Profile 

Add a new collection profile.

For more information, see Adding collection profile.

Modify Collection Profile

Edit the selected collection profile.

You can modify the same details that you provided while adding a collection profile.

Delete Collection ProfileDelete the selected collection profile.

The Collection Profiles tab provides the following information:

FieldDescription
NameName of the collection profile configured.
DescriptionDescription of the collection profile configured.

Creating a collection profile

  1. Navigate to Administration > Collection Profiles.
  2. Click Add Collection Profile
  3. In the Name field, provide an appropriate name to identify the collection profile.
  4. (Optional) In the Description field, provide additional information about the collection profile.
  5. Click Create Data Collector Template to add data collector templates in one of the following ways:

    OptionActionProcedure
    1Search for an existing data collector and use its input parameters for creating a new data collector template.
    1. On the search bar, search for an existing data collector by entering its name.
    2. Select one of the appropriate names displayed in the search suggestions
      The input parameters are automatically populated.
    3. Click Create.
    2Create a new data collector template by manually providing the input parameters.
    1. Instance Name: Provide an appropriate name to identify the data collector template.
    2. Type: Select one of the following options, provide the necessary collector inputs, and click Create:
  6. Click Create.

Where to go from here

Associate the collection profile with the appropriate hosts. For more information, see Managing hosts.

Related topics

 Managing content packs

 Using the command line to export a data collector

 Using the command line to import a data collector