Bigeye Agent CLI
The Bigeye agent CLI is a CLI tool to help Bigeye customers install our Data source, Lineage Plus, and Data health agents. The Bigeye Agent Installer will walk customers through an end-to-end installation process of our agents and validate information is entered correctly. The purpose of this CLI tool is to help expedite the process of installing Bigeye agents.
Requirements
Pre-install checklist
-
Set up a VM / host
- Review the pre-install checklist for the desired agent(s) for infrastructure, networking, and access requirements
- For multiple agents on the same VM:
- 32 GB memory
- 4 cores
- 80 GB disk space
Installation
The Bigeye agent installer utilizes docker for all agents. While agents can run on other platforms, the installer only uses docker for running agents.
Docker
- The CLI can attempt to install docker for users
- Download the installer for your version of Linux or Windows
# RHEL
wget https://bigeye-public-web.s3.us-west-2.amazonaws.com/bigeye-agent-installer/latest/rhel/bigeye-agent
# Ubuntu
wget https://bigeye-public-web.s3.us-west-2.amazonaws.com/bigeye-agent-installer/latest/linux/bigeye-agent
# OS X
wget https://bigeye-public-web.s3.us-west-2.amazonaws.com/bigeye-agent-installer/latest/mac/bigeye-agent
# Windows
curl -O https://bigeye-public-web.s3.us-west-2.amazonaws.com/bigeye-agent-installer/latest/windows/bigeye-agent.exe
- Update permissions to run the installer
# Extract the archive
tar -xf bigeye-agent
# Update permissions
chmod +x bigeye-agent
Running the installer
- View the different commands available with
--helpflag
./bigeye-agent --help
# You can also pass the help flag for specific commands
./bigeye-agent install --help
Usage: bigeye-agent install [OPTIONS]
Walk through installation process of any Bigeye agent.
# Run the installation
./bigeye-agent install
Bigeye Agent Installer
.. ..
...... ......
..... .....
..... ...... ............. ...
..... .......... ..... .... ....
.... .... ... ..... .... ... ... .............. .......... ... .... ..........
. .... ... .. ............. ... ..... ..... .... ........ ........ .....
.. .... ... .. ............... ... .... .................... ... .... ...............
..... .... ... ...... .... .... ... .... ......... .... .... ...
..... .......... ..... .... ..... ... ............... .... ..... ...... .... ....
..... ...... ............. ... .... ..... ..... .......... ..... .........
..... ..... ..... ..... ....
..... ...... ......... ....
? Please choose an Agent option from the list below (Use arrow keys)
» LINEAGE_PLUS
SOURCE
DATAHEALTH
Troubleshooting
[PYI-13495:ERROR] Failed to load Python shared library '/tmp/_MEID1H6U6/libpython3.10.so.1.0': dlopen: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/_MEID1H6U6/libpython3.10.so.1.0)
The binary produced by pyinstaller depends on GLIBC and the version of GLIBC it depends on is based on the OS where the executable gets generated. This error indicates the the version of GLIBC used is not supported by the OS. If possible, provision a VM with a newer version of the OS. Otherwise, Bigeye will need to build a specific version of the installer for the operating system.
jdk.JdkError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)>
Python might not automatically use the updated certificates. You can ensure Python uses the system's CA certificates by setting the SSL_CERT_FILE environment variable. This will tell Python to use the system's certificate bundle for SSL verification.
# Update path if system CA is located elsewhere.
export SSL_CERT_FILE=/etc/pki/tls/certs/ca-bundle.crt
Updated 8 days ago