- Site Collector Overview
- Get Started with Site Collectors
- Install Site Collector
- Set Up Collectors
- Sign Up for the Early Access Program: Site Collectors
- Set Up Archive Windows Collector
- Set Up Archive Linux Collector
- Set Up EStreamer Collector
- Set Up Fortinet Collector
- Set Up IBM Security QRadar Collector
- Set Up Kafka Collector
- Set Up Splunk Collector
- Set Up Linux File Collector
- Set Up Microsoft SQL Collector
- Set Up MySQL Collector
- Set Up Oracle Collector
- Set Up Syslog Collector
- Set Up Windows Active Directory Collector
- Set Up Windows Event Log Collector
- Set Up Windows File Collector
- Manage Site Collectors
- Site Collector Monitoring
- Troubleshoot the Site Collector
- Pre-checks failed during Site Collector installation and upgrade
- Site Collector UI shows the status INSTALLATION_ERROR
- Download Support Packages for Troubleshooting
- How to reboot the Virtual Machine (VM) successfully to apply security updates?
- What information must be added while creating a support ticket to resolve an issue?
- Site Collector UI is not displaying the heartbeats
- Splunk Collector can't be set up
- Splunk Collector is set up however, logs are not reaching DL/AA
- Only a few of the installed Splunk Collectors are processing logs or EPS has dropped by 50% as compared to last hour
- The Windows Active Directory Collector (formerly known as LDAP Collector) is set up, however, the context data is not reaching DL/AA
- The Windows Active Directory Collector (formerly known as LDAP Collector) is stuck in the ‘Update’ mode after deployment
- Installation is initiated; however, the collector shows the status as ‘Setting Up’ for some time
- Data Lake and Advanced Analytics Does Not Show Context Data
- Context Data from Windows Active Directory Collector is Segmented
- Minifi Permission Denied - Logback.xml File Missing and Config File Update - Failed Error Occurred while Installing the Windows Event Log Collector
- Where should I upload proxy certificates if I am running proxy with TLS interception?
- How to upgrade Linux collector instance?
Upgrade the Site Collector
To upgrade an Site Collector instance:
Log in to the Exabeam Security Operations Platform with your registered credentials.
Navigate to Settings > Site Collectors > Site Collectors Instances.
For the instance that you want to upgrade, click Upgrade in the COLLECTOR INSTANCE NAME column.
Note
Upgrade requires tmux version 1.9 or later. If you want to manage tmux upgrade manually, upgrade tmux before upgrading Site Collector. Otherwise, tmux and its dependency is installed and upgraded automatically during Site Collector installation.
To upgrade the site collector to the latest version and restart all associated collectors, click Upgrade.
The Site Collector (SC) Core downloads a new version of Self Extracting Binary (SXB) from the Site Collector app and completes self-upgrade by performing the following actions:
Updates the Site Collector status to UPGRADING
Stops all the flows including the heartbeats to be sent
Creates back-ups for all the configurations
Performs upgrade and applies all the required configuration changes
Updates the Site Collector status to RESTRATING
Restarts all services
Displays the status as RUNNING after the upgrade is completed
Note
If the upgrade process completes successfully, all Collectors in Site Collector including those responsible for management and monitoring, are restarted and the configurations are then reapplied to each of them. The upgrade process takes up to 15 minutes to complete. In case of upgrade failure, Site Collector will be rolled back to the initial version.