The Data Collector is responsible for collecting metrics from “External” sources such as VMware vCenter, Citrix Delivery Controllers, XenServer Poolmasters, AHV Clusters, and NetScaler appliances. Having a data collector will increase the performance capabilities of both your console & monitor.
What does having a data collector means?
Looking at the images below, on the left side, we see 2 consoles and a monitor both connected straight to the vCenter without a DC (data collector). Each of these components is each initiating its own API query to vCenter to gather data.
In this method, the API gets 3 API queries each interval and in very large environments, the traffic can be substantial.
On the right side, we have a data collector. With a data collector deployed, the only entity that does the API query is the data collector and it saves the data locally on the machines memory buffer. The consoles & monitor, which are connected to the agent on the data collector (light connection), can read the data from the agent itself instead of performing their own API queries.
*Example shows 443 but can also be referred to 80\9440
Data Collector requirements -
- A data collector will be assigned with 2-4 vCPUs and 8 GB of RAM. (view the Sizing Guidelines article for exact sizing information).
- The OS can be either a client or server.
- The machine must have the ControlUp Agent installed on.
- .Net Framework v4.5
- Port-wise you should enable 80\443\9440 based on the type of connection.
- A pair of data collector can be provided for HA purposes.
- In the event of a failure of the data collector, a backup data collector will assume this role until the data collector is brought back online.
- SDKs from Citrix will need to be deployed to the Data Collector in order to connect to the XenDesktop Delivery Controllers (you can download it from the following article).
If you have more than 5 external sources to connect to a data collector, please contact us for sizing recommendations at firstname.lastname@example.org