Collecting data from an agentless data source
140 Perceive Getting Started
To select agentless computers, type the beginning and ending IP addresses in the
Beginning IP address and Ending IP address text boxes. Make sure the proxy host you
are trying to find is within the specified IP address range.
After you activate the Agent History data source, Perceive finds all the agents within
the requested IP address range. For each agent that is also acting as a proxy host,
Perceive discovers the agentless computers available from that proxy host. During
this discovery, a list of computer names is retrieved, including all the names of the
agentless systems connected to that proxy host (and the name of the proxy host itself).
The first time an Agent History data source is activated, the list of discovered systems
is stored in the Perceive configuration file
<tomcat_home>/webapps/qtv/WEB-INF/config.xml. In order to speed up the activation
process, if the data source is later deactivated and then activated without being
updated, Perceive uses the list of systems stored in the configuration file.
You can click
Refresh on an agent data source to perform IP discovery. Perceive
automatically performs IP discovery every day during the data source refresh cycle.
To better understand how Perceive discovers agentless computers from a proxy host,
refer to the example in “
User scenario: single IP address” on page 140.
For more information on agentless data collection through a Performance Assurance
proxy host, refer to the Collecting Data with PATROL
®
Performance Assurance
®
guide.
User scenario: single IP address
Let’s say you want to display agentless data in Perceive from a proxy host, and you
have the following configuration:
■ One remote data source activated with a single IP address of a proxy host.
■ The proxy host is configured to collect data from four agentless systems.
■ Some of the agentless systems may have agents installed and running.
NOTE
The History span field in the New Data Source area applies only to the Perceive
configuration, not the PATROL for Performance Manager history configuration.
NOTE
When you try to access data from a proxy host, it might take more time to access
the data in Perceive. This is a limitation of the performance of a proxy host when
several systems access that host simultaneously. The appendix in the Collecting
Data with PATROL
®
Performance Assurance
®
guide provides sizing guidelines that
help you compute the amount of resources necessary to run a proxy collection agent.
