Installing agent for Solaris VM

Installing agents for Solaris - Version 6.0.0 (Latest)

Prerequisites

  • For prerequisite checks for agent installation, see Prerequisite checks for agent installation.
  • OS: Oracle Solaris. See Supported OS Versions
  • SixthSense Infra Agent. See Download the Agent, Configure the Agent, Start the Agent.
  • URL/IP of the Sixthsense collector (your tenant URL provided by Customer Support)
  • Access token provided by Customer Support.
  • PACKAGE_TOKEN - Access Token required for downloading SixthSense Package provided by Customer Support.
  • PACKAGE_TOKEN_USERNAME - Username for Access Token provided by Customer Support.
  • TOKEN - Access Token from the SixthSense portal Settings page.
  • For supported agent versions and framework, see VM agents.

Download & Unzip the agent

  1. Download latest ss_infra_agent_6.0.0.zip release binary provided by Customer Support.
export PACKAGE_TOKEN="token"
export AGENT_VERSION="6.0.0"
curl --header "PRIVATE-TOKEN:${PACKAGE_TOKEN}" --output ss_infra_agent_${AGENT_VERSION}.zip "https://artifacts-observability.sixthsense.rakuten.com/api/v4/projects/15/packages/generic/sixthsense-infra-agent/${AGENT_VERSION}/ss_infra_agent_${AGENT_VERSION}.zip"
  1. Unzip release binary and go to the agent directory.
unzip ss_infra_agent_${AGENT_VERSION}.zip
cd ss_infra_agent_${AGENT_VERSION}
  1. Copy the agent binary and ss_config.yaml to the following directory
  • /usr/local/bin
  1. Give permission to the binary, configuration file for all.
  • sudo chmod +x /usr/local/bin/ss_infra_agent_6.0.0/ss_infra_agent_solaris_amd64 # See Supported Architecture
  • sudo chmod +x /usr/local/bin/ss_infra_agent_6.0.0/ss-config.yaml

Configure the agent

Update ss_config.yaml as per the instructions mentioned in the configuration file.

# sixthsense-infra-agent can be configured via yaml
global_settings:
# A service name groups together all machines that run the same service.
service_name: <Solaris_VM>
# To establish communication between the Infrastructure Agent and the SixthSense backend, authentication is performed using an access token. Login to Sixthsense UI --> On Side Navigation bar Go to Settings --> Copy Access Token.
authentication: <xxxxxx>
# The endpoint of the backend that collects and processes telemetry data from agents.
sixthsense_backend: grpc-collector-observability.sixthsense.rakuten.com:443
# Enables TLS encryption for secure communication with the backend. Allowed values: true|false.
secure: true
# S for Solaris
type: S
# Specifies the logging level for the agent. This helps control the amount of diagnostic data written to logs. Allowed values: debug|error|info.
logLevel: error
# Specifies the directory or file path where logs are stored.
logPath: <vm_agent.log>
# Sets the maximum number of processes the agent will monitor concurrently.
maxProcessLimit: 10
# Port for pprof profiling of agent.(Optional)
# pprofPort: 6060
# Sets the memory usage cap (in MB) for the agent to prevent overconsumption of system resources.(Optional)
# maxMemoryUsageLimit: 1024 # MB
# Sets how often performance data is collected and reported by the agent in seconds.(Optional)
# perfInterval: 60 # seconds

Start the agent

Start the agent directly using nohup

To start the agent, use the following command.

nohup ./usr/local/bin/ss_infra_agent_6.0.0/ss_infra_agent_solaris_amd64 &

In case of network restrictions, append proxy to the nohup command to enable connection to sixthsense-backend.

nohup HTTPS_PROXY=proxy-server:port ./usr/local/bin/ss_infra_agent_6.0.0/ss_infra_agent_solaris_amd64 &
  • nohup - to start with logs, logs will be stored in nohup.out file
  • "&" - to start as background process

Check the logs

Logs Directory

<agent_directory>/logs
Default:/usr/local/bin/ss_infra_agent_6.0.0/logs

Verify that agent is reporting to Sixthsense : Validate Agent Reporting

Stop the agent

Stop/Kill the agent started using nohup

kill -9 $(pgrep infra_agent)