In sensitive production environments, OverOps allows the Agent to communicate with the Collector via sockets instead of shared memory. This reduces CPU and RAM footprints as the OverOps Collector is installed separately from the production machines. Depending on the applied deployment, the Collector can be installed on the Shark cluster (On-premises mode), on the Storage Server (Hybrid mode) or in any other machine available (SaaS mode).
When installing OverOps components on different machines, you may not have root access to all machines. This article describes OverOps installation without root access. The procedure requires you to make some manual adjustments.
The OverOps Collector can also be installed without root access.
Note: Currently, Rootless Collector installation is not supported on Windows.
To install a Collector without root access:
- From get.takipi.com/takipi-latest.tar.gz, download the Collector installation TAR file.
- Extract files to your working folder:
tar -xf takipi-latest.tar.gzA ‘takipi’ folder is created.
- If you do not possess an Installation key, from the OverOps web application, generate an installation key.
- Copy the installation key and paste it into a text file named secret.key.
- Save the secret.key file in the <PATH>/takipi/work directory on your machine.
- According to the template below, create the collector.properties file:
# The TCP port to listen on
# Used by both Collector & Agent, Arbitrary token used to identify the Agent against the Service
# The server name of the Collector. Leave empty for HOSTNAME
# The internal JVM max heap size
- Place the properties file in the takipi directory on your machine.
- Run the Collector:
- Test the installation:From the OverOps web application (app.overops.com) Dashboard, click Add Server and then, from the dialog box, click Next and then click Test Installation.
When the connection is established, the Collector status is 'Monitoring'.
- Test that your application throws exceptions.
Rootless installation does not enable the Collector to start automatically after a reboot.
- Run the Collector as a daemon according to your system.
To install the Agent without sudo:
- From, get.takipi.com/takipi-latest.tar.gz, download the Agent installation TAR file.
- Extract files to your working folder.
A 'takipi' folder is created.
- Edit the agent.properties file and set:
- serverName: the machine name, usually this is the output of echo `hostname`.
- masterHost: the Collector host.
- masterPort: the Collector port.
- Start your application with -agentpath and full path:
java -agentpath:/home/user/takipi/lib/libTakipiAgent.so -jar sample.jar arg1
OverOps supports multiple Collectors that can be configured for high-availability and/or for load balancing. For high-availability, traffic is routed as round-robin according to the master endpoint configuration, as described below. For load balancing, routing depends on the load-balancer policy settings.
Note: Collector high-availability is not supported on macOS.
To configure Collector high-availability:
- From the Agent, open the agent.properties file and add the Collector Endpoints:
- Leave masterHost and masterPort empty.
- Save and close the properties file.
To configure load balancing for multiple Collectors, see Load Balancing with Nginx as an example.