Links

Agent V1 (legacy)

StackState Self-hosted v5.1.x
Agent V1 (legacy) will be deprecated in a future release of StackState.
If you are still running Agent V1 (legacy), it is advised that you upgrade to Agent V2 and migrate all checks to run on Agent V2.

Overview

Prior to StackState v5.1, Agent V1 (legacy) was used to run checks that connect to Splunk to retrieve metrics and events data. From StackState v5.1, all Agent checks run on StackState Agent V2.
StackState Agent V1 (legacy) is open source: View the source code on GitHub.

Installation

Agent V1 (legacy) will be deprecated in a future release of StackState.
It is advised that you install Agent V2 and migrate all checks to run on Agent V2.
Install StackState Agent V1 (legacy) by using the following sequence of steps:
Debian, Ubuntu
Amazon linux, CentOS, Fedora, Red Hat
  1. 1.
    Download the StackState Agent V1 (legacy) Debian package or run this command on the machine where you wish to install the Agent:
    wget https://s3-eu-west-1.amazonaws.com/agent.stackstate.com/stackstate-agent-deb-repo/pool/s/stackstate-agent/stackstate-agent_1.3.0-1_amd64.deb'
  2. 2.
    Use dpkg to install the downloaded package:
    dpkg -i stackstate-agent_1.3.0-1_amd64.deb
  3. 3.
    Set the following keys in the stackstate.conf.example file:
    api_key: {{config.apiKey}}
    dd_url: {{config.baseUrl}}/stsAgent/
  4. 4.
    After this the example configuration can be used as configuration.
    cp /etc/sts-agent/stackstate.conf.example /etc/sts-agent/stackstate.conf
  1. 1.
    Download the StackState Agent V1 (legacy) RPM package or run this command on the machine where you wish to install the Agent:
    wget 'https://s3-eu-west-1.amazonaws.com/agent.stackstate.com/stackstate-agent-yum-repo/stackstate-agent_1.3.0-1.x86_64.rpm'
  2. 2.
    Use rpm to install the downloaded package:
    rpm -i stackstate-agent_1.3.0-1.x86_64.rpm
  3. 3.
    Set the following keys in the stackstate.conf.example file:
    api_key: {{config.apiKey}}
    dd_url: {{config.baseUrl}}/stsAgent
  4. 4.
    After this the example configuration can be used as configuration.
    cp /etc/sts-agent/stackstate.conf.example /etc/sts-agent/stackstate.conf
If you need further assistance, our support team will be glad to help.

Start / stop / restart the Agent

  • Commands require elevated privileges.
  • Restarting StackState Agent V1 (legacy) will reload the configuration files.
To manually start, stop or restart StackState Agent V1 (legacy):
Linux
Windows
sudo /etc/init.d/stackstate-agent start
sudo /etc/init.d/stackstate-agent stop
sudo /etc/init.d/stackstate-agent restart
CMD
"C:\Program Files\StackState\StackState Agent\embedded\agent.exe" start-service
"C:\Program Files\StackState\StackState Agent\embedded\agent.exe" stopservice
"C:\Program Files\StackState\StackState Agent\embedded\agent.exe" restart-service
PowerShell
& "C:\Program Files\StackState\StackState Agent\embedded\agent.exe" start-service
& "C:\Program Files\StackState\StackState Agent\embedded\agent.exe" stopservice
& "C:\Program Files\StackState\StackState Agent\embedded\agent.exe" restart-service

Status and information

Linux
Windows
To check if StackState Agent V1 (legacy) is running:
sudo /etc/init.d/stackstate-agent status
To receive information about the StackState Agent V1 (legacy) state:
sudo /etc/init.d/stackstate-agent info
Tracebacks for errors can be retrieved by setting the -v flag:
sudo /etc/init.d/stackstate-agent info -v
To check if the StackState Agent V1 (legacy) is running and receive information about the Agent's state:
"./agent.exe status"

Troubleshooting

Try running the info command to see the state of StackState Agent V1 (legacy).
Logs for the subsystems are in the following files:
  • /var/log/stackstate/supervisord.log
  • /var/log/stackstate/collector.log
  • /var/log/stackstate/stsstatsd.log
  • /var/log/stackstate/forwarder.log
If you are still having trouble, contact our support team on the StackState support site.

See also