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 data collector templates by manually providing all the inputs or by using an existing data collector inputs. 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.
Collection profiles can also be associated with Collection Agents by using BMC PATROL for IT Data Analytics in one of the following ways:
At the time of configuring collection Agents, you can specify a collection profile name that already exists under the Collection Profiles tab. It is important that the collection profile you want to associate already has groups access permissions defined. Without this, all the users will be able to see the data collectors created through such a collection profile irrespective of their role.
You can also override existing macro values while associating a collection profile.
Note
Creation of collection profile 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.
This topic contains the following information:
A collection profile has the following advantages:
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:
Macros can be defined as objects that store values that can be referred by the data collector templates at the time of creating data collectors. At the time of adding data collector templates, you can specify macro names instead of manually providing input parameters. When the data collectors are created on the basis of the data collector templates, the macro values are substituted for the fields in which you specified macro names. To be able to specify macros while adding data collector templates, you need to first add them under the Macros section by providing a macro name and a corresponding macro value.
Using macros helps you define common input parameters (such as directory path, file name, tag values, and so on) at one time and then reuse that information each time you want to create a data collector template. It is also useful if you want to modify the values of common input parameters together without having to edit each data collector template and manually modify values.
Additionally, you can override macro values in the following ways:
Note
While specifying macro names as input parameters, you need to specify the macro name in the format, ${MacroName}.
The MacroName refers to the macro name displayed in the list of added macros.
Macros are supported only for the following fields:
Supported fields | Data collectors applicable |
---|---|
| All |
| Receive over TCP/UDP |
While adding macros, the following conditions apply:
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:
Action | Icon | Description |
---|---|---|
Add Collection Profile | Add a new collection profile. For more information, see Adding collection profile. | |
Edit Collection Profile | Edit the selected collection profile. You can modify the same details that you provided while adding a collection profile. | |
Delete Collection Profile | Delete the selected collection profile. |
The Collection Profiles tab provides the following information:
Field | Description |
---|---|
Name | Name of the collection profile configured. |
Description | Description of the collection profile configured. |
Click
Create Data Collector Template to add data collector templates in one of the following ways:Recommendation
BMC recommends you to use option 1 for creating the data collector templates if you do not know the specific data pattern necessary for the data that you want to collect. If you create a data collector first, then you can easily find the relevant data pattern by using the filter and preview options available. You can then use the inputs of this data collector for creating the data collector templates.
Option | Action | Procedure |
---|---|---|
1 | Search for an existing data collector and use its input parameters for creating a new data collector template. |
|
2 | Create a new data collector template by manually providing the input parameters. |
|
Associate the collection profile with the appropriate hosts. For more information, see Managing hosts.