Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Help
  3. Section VIII. Data Collector Installation and Configuration
  4. Install and configure a Data Collector
  5. Step-3: Add Data Collector on IT Analytics Portal

Step-3: Add Data Collector on IT Analytics Portal

Once logged in to the Portal:

  1. Select Admin > Data Collection > Collector Administration.
  2. Click Add Collector.

    On the Add Collector screen, you will need to define the Collector Name, Passcode and select the IT Analytics Domain you wish to associate with the Collector and your Auto-upgrade options. Please refer to the table below for additional details regarding each field.

    Although the Data Collector name can be anything, Cohesity recommends that the Data Collector name be the hostname of the server the Data Collector software is installed on. In the example below, we use the Data Collector Server Name followed by "_DC".

    Field

    Description

    Collector Name*

    The collector name cannot include a space and is case sensitive. The names should match exactly as entered in the Data Collector configuration screen and the Data Collector Installer screen.

    Edit the unique name assigned to this Data Collector. The Data Collector will use this value for authentication purposes.

    Changing the Collector ID or passcode requires manual changes to the corresponding Data Collector server. Collection will break if these corresponding changes are not made.

    Passcode*

    Edit the passcode assigned to this Data Collector. It can be any character sequence.

    Unlike other system passwords (which are encrypted and then saved) this Data Collector passcode is not encrypted prior to saving in the database and may appear as clear case in certain files. It simply is intended as a "handshake" identification between the Data Collector and the policy.

    Changing the Collector ID or passcode requires manual changes to the corresponding Data Collector server. Collection will break if these corresponding changes are not made.

    You can use the following OS-specific special characters in the passcode. Make sure the special characters you include are supported on the OS where the Data Collector is installed.

    • Linux: !@#%^*

    • Windows: !@#$%^&*()

    Short Notes

    Descriptive notes associated with this Data Collector.

    Enable SSL

    Both secure (SSL) and non-secure Data Collectors can send data to the same Portal. Check this box to select the secure communication protocol (https) that the Data Collector will use.

    This check box will not appear in the dialog box if SSL is not enabled in your environment. The Portal data receiver must be listening for https traffic; for example: https://agent.mycollector.com

    Auto-upgrade aptare.jar

    Indicate if you want this configuration file upgraded automatically.

    This part of the Data Collector is responsible for event and metadata processing threads. The .jar file contains the processing and parsing logic for data collection. The latest versions can be downloaded automatically and applied to the collector during upgrades. It is recommended that this setting be set to Yes.

    Auto-upgrade Upgrade Manager

    Indicate if you want this configuration bundle upgraded automatically.

    This Data Collector component is responsible for managing Data Collector upgrades. The latest versions can be downloaded automatically and applied to the collector during upgrades. It is recommended that this setting be set to Yes.

  3. Click OK.

    You will now be presented with the following message, indicating that a .json file has been created. This file is required when you configure and register your Data Collector.

  4. Click OK.

Feedback

Was this page helpful?
Previous

Step-2: HTTPS requirement

Next

Step-4: Install the Data Collector

Feedback

Was this page helpful?