OpsRamp Collector Bootstrap Tool

Overview

OpsRamp’s collector bootstrap is a small and flexible tool designed to simplify and automate day-0 onboarding of all OpsRamp’s collector technologies - agent, gateway into myriad of IT environments - bare-metal, virtualized, containerized and cloud-native environments on various host Linux OS be it either on-prem or in the public cloud.

Once you download the right binary from the cloud platform into your target operating system - Linux, you can instruct the tool via its command line interface (CLI) to kickstart the collector installation. In a single command, the tool not only verifies the host environment that will eventually house the collector but also automates what are currently manual steps around authentication and registration of the collector with the cloud platform. The tool can be optionally instructed, in the same command, to start infrastructure discovery automatically without requiring any additional configuration on the cloud side.

Download the Collector Bootstrap Tool

While the collector bootstrap tool can be downloaded into any machine (into your laptop, for example), the tool is expected to be executed from the same host as you will eventually run the collector.

To download the Collector Bootstrap Tool, follow these steps:

1. From All Clients, select a client.

2. Go to Setup > Account > Collector Profile.

3. Click + ADD on the COLLECTOR PROFILES page.

• Linux ARM
• Linux AMD
• Mac ARM
• Mac AMD
• Windows AMD

8. Run the wget command provided on the instruction page to download the gateway. The command varies based on the selected architecture.

opsramp-collector-start --version

Available Commands

Available Flag

Use Bootstrap Tool to Install the NextGen Gateway

This section describes how to install and uninstall the NextGen gateway using the bootstrap tool.

Step-1: Available flags for installing nextgen gateway

Use the following command to see the available flags. The collector bootstrap needs sudo privileges.

opsramp-collector-start install --help

Flags for installation commands

Step-2: Get the activation token

To find the activation token and API server url, navigate to Setup > Resources > Management Profile and click on the name of your newly created profile.

Activation auth token: 55c803a1-2e2f-4c07-be95-479dc8fdf7ff

Cloud url API server: gatewaytest.api.opsramp.net

Step-3: Registering the nextgen gateway

Option 1: Registering the nextgen gateway without proxy

opsramp-collector-start install --environment k8s --url {OpsRamp Server URL} --key {Gateway unique authentication token}

Installing gateway in a kubernetes environment:

Option 2: Registering nextgen gateway through proxy

Often customers will not be allowed to connect to their network directly for security reasons, customers will install proxy in their environment and will allow the third party users to connect to their network through proxy.

OpsRamp Gateways are deployed in customer environments, so in order to connect to an outside network from Gateway it needs to pass through a proxy.

The customers who have proxies installed in their environment, need to use the below gateway installation command for registration.

The examples below show how to register the gateway through proxy method. The collector will try to register the gateway, once it’s installed, through the proxy. The tool supports registration with or without credentials as shown below:

• Register through proxy with credentials.

  opsramp-collector-start install --environment {Environment} --url {OpsRamp Server URL} --key {Gateway unique authentication token} --proxy-protocol {Proxy Protocol http/https} --proxy-ip {Proxy IP Address} --proxy-port {Proxy Port} --proxy-username {Proxy Username} --proxy-password {Proxy Password}

• Register through proxy without credentials.

  opsramp-collector-start install --environment {Environment} --url {OpsRamp Server URL} --key {Gateway unique authentication token} --proxy-protocol {Proxy Protocol http/https} --proxy-ip {Proxy IP Address} --proxy-port {Proxy Port}

Option 3: Registering nextgen gateway by using yaml config file

Users can register the NextGen gateway by using registration flags within a YAML file.
To complete the registration process, follow these steps:

1. Generate a YAML file based on the provided sample YAML below and make the required modifications:

Sample YAML

config:
squid-proxy: disable
third-party-app: disable
 
proxy:
  proxy-protocol:
  proxy-ip:
  proxy-port:
  proxy-username:
  proxy-password:
 
helmchart-version: 1.6.0
 
repo:
  repository:
  repo-user:
  repo-password:
  read-repopass-from-file:
 
gateway-name:
storage-class:

#Pass the snmp_v3 credentials in below format. Put 2 spaces under the "snmp_trap_v3_credentials" and pass the keys after those spaces (spaces are for yaml intonations)
#snmp_trap_v3_credentials: |-
#  key1
#  key2
#  key3
# Refer https://docs.opsramp.com/platform-features/feature-guides/monitoring-using-snmp-traps/#configure-snmp-v3-traps for more details on configuring SNMP credentials.
 
snmp_trap_v3_credentials: |-
 
vprobe:
  resources:
    limits:
      memory: "5096Mi"
 
nativebridge:
  resources:
    limits:
      memory: "500Mi"
 
squid:
  resources:
    limits:
      memory: "500Mi"
       
postgres:
  resources:
    limits:
      memory: "1024Mi"

opsramp-collector-start install --url uat.opsramp.net --key 2e245f6b-0056-4ad3-84e7-1553f42af1be --registration-config /home/e0421@opsramp-corp.com/git/nextgenConfig.yaml

Step-4: Check for successful gateway registration

Once the CLI returns successfully, navigate to Setup > Resource > Management Profile to check if the gateway registered successfully.

Gateway connection status:

Use Bootstrap Tool to Uninstall the NextGen Gateway

Use the following commands to uninstall the NextGen gateway using bootstrap tool.

sudo opsramp-collector-start uninstall -e {Environment}

Available Flags

Uninstallation of kubernetes.

Once the CLI returns successfully, navigate to Setup > Resource > Management Profile to check if the gateway is de-registered successfully.

Gateway connection status:

Troubleshooting

Following are the errors if any CLI failures.

• If you are providing the incorrect cloud api server url:

  

• If you are trying to re-registering gateway:

  

• If the Kubernetes server is not reachable: