Installation on Linux
This section provides the installation steps for NetObserv Flow. Many users get started using ElastiFlow with the Elastic Stack (Elasticsearch and Kibana). To install and configure both the Elastic Stack and NetObserv Flow, step-by-step instructions are provided for both Ubuntu/Debian and RedHat/AlmaLinux.
NetObserv Flow can be installed natively on Linux. Packages are currently provided for and supported on the Linux distributions and versions listed in the following table.
Ubuntu
22.04 LTS, 24.04 LTS
Debian
12
RHEL/RockyLinux/AlmaLinux
8.x, 9.x
Ubuntu/Debian Installation (deb)
The Debian package for the NetObserv Flow can be downloaded from here. It can be used for installation on most Debian-based systems such as Debian and Ubuntu.
Download the .deb Package
.deb PackageThe package can be downloaded using either the wget or curl command:
Verify the Package
Checksum Verification
To ensure the downloaded file was fully downloaded and wasn't corrupted or tampered with, you can verify the provided checksum matches.
GPG Verification
ElastiFlow signs the Debian package with a GNU Privacy Guard (GPG) key. To verify the Debian package, download and import the ElastiFlow GPG public key:
Next, download the signature file:
Finally, verify the file with the signature:
Ensure that libpcap-dev and ca-certificates are Installed
libpcap-dev and ca-certificates are InstalledThe collector requires libpcap-dev and ca-certificates. Check if the packages are installed:
If installed, the output will look similar to the following:
If the packages are not present, install them:
Install the .deb Package
.deb PackageThere are two methods to install the NetObserv Flow package, apt or dpkg.
Install with apt
Install with dpkg
RedHat/AlmaLinux Installation (rpm)
The RPM package for NetObserv Flow can be downloaded here. It can be used for installation on most RedHat-based systems such as RHEL and CentOS.
Download the .rpm Package
.rpm PackageThe package can be easily downloaded using wget or curl:
Verify the Package
Checksum Verification
To ensure the downloaded file was fully downloaded and wasn't corrupted or tampered with, you can verify the provided checksum matches.
GPG Verification
ElastiFlow signs the RPM package with a GNU Privacy Guard (GPG) key. To verify the RPM package, download and import the ElastiFlow GPG public key:
Next, download the signature file:
Finally, verify the file with the signature:
Ensure that libpcap, libpcap-devel and ca-certificates are Installed
libpcap, libpcap-devel and ca-certificates are InstalledThe collector requires libpcap, libpcap-devel and ca-certificates. Check if the packages are installed:
If installed, the output will look similar to the following:
If the packages are not present, install them:
RHEL 8.x based Distributions
RHEL 9.x based Distributions
Install/Upgrade the .rpm Package
.rpm PackageIf installing the NetObserv Flow package for the first time, i.e. NOT upgrading, run the following:
If upgrading from a previously installed NetObserv Flow package, run the following:
Configuration
The NetObserv Flow will be installed to run as a daemon managed by systemd. Configuration of the collector is provided via environment variables and, depending on the enabled options, via various configuration files which by default are located within /etc/elastiflow.
To configure the NetObserv Flow, edit the file /etc/elastiflow/flowcoll.yml. For details on the configuration options, please refer to the Configuration Reference.
At a minimum the NetObserv Flow must point to a valid data store. Additionally, source flows need to be pointed to the NetObserv Flow so it can pass those along to the data store. The most common installation uses Elasticsearch and Kibana as the data store. To install and configure both the Elastic Stack and NetObserv Flow, step-by-step instructions are provided for both Ubuntu/Debian and RedHat/AlmaLinux.
Running the Collector
To start the collector, execute the follow commands:
To ensure the collector has started and is running, execute:
The collector can be stopped using:
If you want the collector to be started automatically when the system is booted, it must be enabled:
Last updated
Was this helpful?
