Collecting data via Capacity Agents

You can use Capacity Agents to collect data from the managed systems in your environment. The managed systems include physical systems and systems that run on the virtualized platforms, such as AIX, HP, KVM, and Solaris. The data collected by the Capacity Agents is transferred to the Gateway Server, which processes the data. The processed data is transferred to the Application Server and then to the database. You can view this data in the views and analyze it for investigating the capacity-related issues in the managed systems.

Additionally, you can configure the Gateway Server to aggregate and store the process-level data from the Capacity Agents. This process-level data can be accessed from the Process Profile page in the Data Explorer view for AIX, KVM and Solaris in the TrueSight console.

To collect data using Capacity Agents, complete the following tasks:

I. Complete the prerequisite tasks.

II. Add the agent list to the Gateway Server.

III. Schedule the new Manager runs.

IV. Check the status of Manager runs.

V. View the Gateway Server reports.

Step I. Complete the prerequisite tasks.

  1. Install the Gateway Server.
  2. Install Capacity Agents on the required managed systems.
  3. (For AIX systems) To collect data from HMC, see Configure data collection from HMC.

Step II. Add the agent list to the Gateway Server.

The agent list contains a list of managed systems in your environment. Add the agent list to the Gateway Server to automatically create domain files, and Manager runs. Manager runs initiate data collection from the Capacity Agents and store the collected data in the repository.

For more information, see Managing-the-Gateway-Server-agent-list.

(optional) Step III. Configure the Manager runs.

The Manager runs that are automatically created collect data according to the default schedule. You can change this schedule if required. For more information, see Scheduling-new-Manager-runs. 

Step IV. Check the status of Manager runs.

Check the status of Manager runs. For more information, see Recovering-the-Manager-runs.

Step V. View the Gateway Server reports.

View the Gateway reports to check the details related to the status, errors, and exceptions. For more information, see Accessing-Gateway-reports.

After the data is collected from the Capacity Agents, the Gateway Server converts the data to the VIS file format. The ETLs that were created automatically transfer the VIS files to the Application Server.


Applicable for the Linux Gateway Server

When the Linux Gateway Server sends a request to collect data from a managed system that has multiple versions of agents installed but no agent currently running, the Service Daemon on that system will check and attempt to start an agent dynamically in the following order:

  1. It checks for an agent that matches the version of the Gateway Server.
  2. If no matching version is found, it looks for agents with versions earlier than that of the Gateway Server. For example, if the 20.02 agent is not available, it will start by searching for the 11.5 and then the 11.3 versions.
  3. If neither an agent with the same version nor one with an earlier version is found, then the Service Daemon starts the agent mentioned in best1_default.

For this same scenario, when you apply Cumulative Hotfix 9 or later on Patch 2 (20.02.02) of TrueSight Capacity Optimization 20.02, the Linux Gateway Server sends a request and verifies the version of the service daemon running on that system. The service daemon then starts the agent that matches the service daemon version instead of the Gateway Server version. For example, if the managed system has Helix 24.4 and 24.3 and TrueSight 20.02 agents installed and none are currently running, the Linux Gateway Server 20.02 collects data by using the Helix 24.4 agent, which is started by the service daemon.

If the Linux Gateway Server does not receive any agent version from the managed system, it defaults to using the agent that matches the Gateway Server version.


Configure the Gateway Server to aggregate process-level data

Before you begin

Configure the Gateway Server and Capacity Agents to collect data. 


Workflow

gws_process_level_data.png

To configure the Gateway Server to aggregate process-level data

  1. In the TrueSight Capacity Optimization console, select the required Gateway Server.
  2. Schedule process rollup for aggregating and storing process-level data from AIX, KVM and Solaris servers. For more information, see Aggregating process-level data for views.
  3. In the TrueSight console, use the Process Profile page of the Data Explorer views to view the process-level data. For more information, see Using views to analyze infrastructure and virtual data.

Related topics

Collecting-data

Overview-of-ETLs

 

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