GuidesAPI
DocumentationAPICommunitySupportLog In

Install Collector and/or Agent using RPM

Create a Provisioning File

  1. When installing the Java Collector and Micro-Agent with RPM, you'll first need to create a provisioning file that contains the available variables
    If this file doesn't exist, you'll receive a warning notification, and the installation will be performed using the default values instead.
  2. The path of the file varies depending on the operating system you use:
  • Redhat, Centos -
    /etc/sysconfig/takipi
  • Others -
    /etc/default/takipi
  1. You can also change this path using the TAKIPI_INSTALL_CONFIG_FILE environment variable. This variable lets you change the location where OverOps should look for the provisioning file.

Here's an example of a provisioning file that contains all the available variables

#############################
# EXAMPLE PROVISIONING FILE #
#############################
#
TAKIPI_INSTALLATION_TOKEN=
# Optional 
# Only used for Multi Environment Collector (MEC) installation
# Required if you are using MEC
# Provide the MEC token
#
#
TAKIPI_INSTALLATION_KEY=
# Required when not using MEC
# Provide your Installation Key
#
#
TAKIPI_USER_NAME=
TAKIPI_USER_GROUP=
# Optional
# Will CHOWN of /opt/takipi folder to the USER_NAME:USER_GROUP,
# and run takipi-service using USER_NAME.
#
#
TAKIPI_LOG_FOLDER= 
TAKIPI_WORK_FOLDER=
# Optional
# Will create symbolic links pointing /opt/takipi/temp and /opt/takipi/work
# to the folder specified here.
# Leave empty for using default directories
#
#
TAKIPI_BACKEND_URL=
# Required
# For SaaS/Hybrid:
#     https://backend.overops.com
# For On premises:
#     Your backend server http(s)://your_backend_domain:port
#     or load balancer URL
#
#
TAKIPI_SERVER_NAME=`hostname`-collector
# Optional
# Set you collector name
# Default is your collector host name
#
#
TAKIPI_LISTEN_PORT=
# Optional
# Default port is 6060
# provide an alternate port
#
#
TAKIPI_COLLECTOR_HOST=
TAKIPI_COLLECTOR_PORT=
# Required for Agent installation
# Provide Hostname and Port of your collector installation

User and Group Parameters

The following parameters let you install and run the RPM installation as a user or group.

Parameter

Description

Comments

TAKIPI_USER_NAME

Lets you install and run the Collector/Agent with a user.

Changes the Owner of the takipi folder to this TAKIPI_USER_NAME:TAKIPI_USER_GROUP.

When the collector is started the collector will run under this TAKIPI_USER_NAME:TAKIPI_USER_GROUP

TAKIPI_USER_GROUP

Run the Collector/Agent as a group

This is the same as for the user, but usually the parameters will be a combination of user + group (often the same name) - see example below.

Using the user/group parameters affects the permissions of files under /opt/takipi, since the
Systemd Linux Service Manager daemon runs the process with this user/group.

Install OverOps Collector

  1. Download the latest RPM package
    wget --content-disposition https://app.overops.com/app/download?t=rpm

🚧

Be aware that the collector is automatically started after the install completes.

  1. Install the Collector and Agent
    sudo rpm -i takipi-<version>.rpm

👍

Install OverOps in a custom location

By default OverOps is installed in /opt

You can overwrite the default location using the --relocate option
Example:
sudo rpm -i takipi-<version>.rpm --relocate /opt=/opt/overops
Overwrite the default location from /opt/takipi to /opt/overops/takipi

  1. Verify that you're connected to the environment by referring to the top left corner of the your screen.

Update an existing non-RPM installed Collector

  1. Download the latest rpm file or use an previously downloaded version
    wget --content-disposition https://app.overops.com/app/download?t=rpm
  2. Stop the Collector.
  3. Create a Provisioning File in /etc/sysconfig/takipi (as documented above) and map the configuration of the current installation. You'll only need one Collector per instance.
  4. Update the installation via rpm:
    sudo rpm -Uvh takipi-4.45.0.rpm

👍

Installing OverOps into a customer location

By default OverOps is installed in /opt

You can overwrite the default location using the --relocate option
example: sudo rpm -Uvh takipi-<version>.rpm --relocate /opt=/opt/overops
Overwrite the default location from /opt/takipi to /opt/overops/takipi

  1. Verify that the Collector (takipi-service) process is running and check in the OverOps that it's connected.

Micro-Agent Installation (without Collector)

The same RPM Installer can be used to install a Micro-Agent:

  1. Create a provision file (sample below) for the agent installation
    The path of the file varies depending on the operating system you use:
    For Redhat, Centos it is typically /etc/sysconfig/takipi
TAKIPI_COLLECTOR_HOST=
TAKIPI_COLLECTOR_PORT=
# Required
# Provide Hostname and Port of your collector installation
#
#
TAKIPI_USER_NAME=
TAKIPI_USER_GROUP=
# Optional
# Will CHOWN of /opt/takipi folder to the USER_NAME:USER_GROUP,
# Ensure that the application which OverOps will be attached to 
# has full access writes to /opt/takipi folders.
#
#
TAKIPI_LOG_FOLDER= 
# Optional
# Will create symbolic links pointing /opt/takipi/log 
# to the folder specified here.
# Leave empty for using default folder
  1. Install the Agent
    sudo rpm -i takipi-<version>.rpm