The Collector Administration view is a dashboard for data collectors and policies. In addition to the setup and management of Data Collectors and their collection policies, the Collector Administration view enables you to initiate, monitor, edit and validate the live status of your data collection all within the portal.

See also:

In addition to the setup and management of Data Collectors and their collection policies, the Collector Administration view enables you to monitor if data collectors are running and the current status of collection. From this view, you have visibility into the status of both scheduled collection and on-demand runs, with drilldowns to more granular information available on the Collection Status view. See Monitoring Data Collection Status for details.

The Collector Administration view also provides functionality to quickly initiate and validate the collection run, once collectors and policies are setup. Validation methods are initiated differently based on the subsystem vendor associated with the Data Collector policy, but perform essentially the same functions. Refer to Data Collectors: Vendor-Specific Validation Methods for a table of vendor-specific validation methods.

For more information about validation and status refer to:

To enable the Data Collector server to pass data to the Portal server, a corresponding Data Collector must be created in the Portal, along with Data Collector policies for each of the vendor-specific enterprise objects. Data Collector policies are specific to the type of data that is being collected; however, multiple types of policies often can be combined within one Data Collector.

The first step is to create a Data Collector. Once created, you can add policies to it. Often one Portal Data Collector is sufficient for adding Data Collector policies for a variety of enterprise objects such as backup servers, arrays, and switches.

For information about upgrading data collectors, refer to Upgrading Data Collectors.

You can enable and disable a Data Collector through the Portal. When you disable a collector, it stops the service/process running on the data collector server and stops all collection. When collectors are disabled, you can still edit schedules and parameters. To start collection after a Data Collector has been disabled, you must enable the Collector in the Portal, and start the Data Collection service/process on the Data Collector server.

Enable and disable individual data collection policy schedules through the Portal. When you disable a policy, it deactivates the collection schedule. When policies are disabled, you can still edit them.

The status of your Data collection is comprised of multiple conditions, the state of the Collector, is it online or offline, are policy schedules active or stopped, is a scheduled collection run in progress or is an On-Demand run waiting? All of these conditions and others make up the current status of the Data Collector. The Collector Administration view provides this summary-level status. From this view, you have visibility into the status of both scheduled collection and on-demand runs, with drilldowns to more granular information available on the Collection Status view.

Status for collectors and policies are an aggregate value. Any collection failure on a probe, results in a Failure status for the policy, and any failure on a policy results in a Failure status for the Data Collector. When determining a status for a data collector policy, the status of individual probes are rolled up to create a value for the last time collection was attempted. For example, if collection has failed for a certain enabled probe, the status of the policy would be failed.

Due to the nature of certain types of collected data, the Collector Administration view cannot always display states for all collected policies.

The following table lists the exceptions, where the collected subsystems cannot be fully represented in the view.

 

When you delete a Data Collector from the Portal, the collector and any policies associated with it will be deleted from the Portal and the database.

The Data Collector Upgrader provides options to manually upgrade to the latest Data Collector logic. Updates can be downloaded to the Portal server (see To deploy updates to collectors). From the Portal server, you can push the updates out to individual Data Collector servers (see To deploy updates to collectors).

This part of the Data Collector is responsible for event and metadata processing threads.

The Upgrade Manager is responsible for all Data Collector upgrade activities.