Here we'll walk you through the process of setting up the OpsClarity agent on your hosts. We currently support CentOS/RedHat 5.x/6.x/7.x, Ubuntu 12, 14 and 16, and Debian 8. If your host is running another OS, please contact us at firstname.lastname@example.org for additional assistance.
OpsClarity agent runs variations of ps, netstat and netcat commands on the host to collect the information it needs. If you do not have these standard Linux utilities installed on your containers or hosts, you can install them by adding these commands to your host init config.
|netcat||apt-get install -y netcat||yum install -y nc.x86_64|
|netstat||apt-get install -y net-tools||yum install -y net-tools|
|ps||apt-get install -y procps||yum install -y procps|
You will need to log into your OpsClarity account before you begin.
1.) The first step is to install the agent with this command line using root access on each host:
cd /tmp && wget --user=<from-your-opsclarity-welcome-email> --password=<from-your-opsclarity-welcome-email> -N "http://repo.opsclarity.com/archives/agent/release/linux_amd64/agent-installer.sh" && bash ./agent-installer.sh -k "<your-opsclarity-license-key>"
The above command installs the agent with it's embedded collectd running on a default port of 10101. In Cloudera-based environments, the port 10101 is already used by the Alert Manager service from Cloudera Manager. In these cases, the agent should be started with a non-default collectd port using the -p option as shown below.
cd /tmp && wget --user=<from-your-opsclarity-welcome-email> --password=<from-your-opsclarity-welcome-email> -N "http://repo.opsclarity.com/archives/agent/release/linux_amd64/agent-installer.sh" && bash ./agent-installer.sh -k "<your-opsclarity-license-key>" -p 10102
2.) Then grant third party access to Amazon Web Services (AWS) so that more data will be available to OpsClarity. This is used to identify the AWS services you are running, as well as perform anomaly detection on the most relevant metrics. To do this, we'll need read-only third party access using a secure AWS Identity and Access Management (IAM) Role.
There are two pieces of information that you will need to obtain from your installation page in order to turn on AWS access: OpsClarity's AWS Account ID and External ID:
Do note, to obtain the ARN role number, you will need to follow the steps found in this walkthrough: enabling AWS access.
3.) After you have completed step 2, you will see an ARN number on the Review page. Enter your ARN into the field (under step three on the installation page) and click "OK" to complete the installation.
After you have installed the agents, OpsClarity will take a few minutes to create your app topology and infra hostmap. You are now ready to explore your topology and hostmap.
If you have any questions or comments about this article, feel free to contact us at email@example.com.