Operating System
Debian and Ubuntu
The agent has been tested on Ubuntu LTS 14.04/16.04/18.04/20.04/22.04/24.04 and Debian 8/9/10/11/12. First make sure the following packages are installed. All the following commands need root permissions, you might have to usesudo.
/etc/apt/sources.list.d/appsignal_agent.list that contains the repository configuration below for the OS you use.
Ubuntu
Make sure to replacelunar in the appsignal_agent.list config file below with your Ubuntu release’s name. Use the following release names:
noblefor Ubuntu 24.04jammyfor Ubuntu 22.04focalfor Ubuntu 20.04bionicfor Ubuntu 18.04xenialfor Ubuntu 16.04trustyfor Ubuntu 14.04
Debian
Make sure to replacebookworm in the appsignal_agent.list config file below with your Debian release’s name. Use the following release names:
bookwormfor Debian 12bullseyefor Debian 11busterfor Debian 10stretchfor Debian 9jessiefor Debian 8
Install the agent
Then runapt update to get the newly added packages and install the agent.
Redhat Enterprise Linux/Centos
At the moment EL version 7 and 8 are supported. First make sure the following packages are installed. All the following commands need root permissions, you might have to usesudo.
/etc/yum.repos.d/appsignal_agent.repo that contains the repository configuration below for EL7:
Configuration
The standalone agent configuration can be found at/etc/appsignal-agent.conf. For a list of all the available options, see the configuration options page for the standalone agent.
The required Push API key can be found in the “Push & Deploy” section for any app in your organization, and in the “Add app” wizard for your organization.
When configuring the standalone agent, pick an app name and environment that works for you. It can either be a separate app, or you can configure it for an existing app so that it reports as a new host to that app.
- On Ubuntu 14.04 use
service appsignal-agent restart - On Centos/Redhat and Ubuntu 16.04 and up use
systemctl restart appsignal-agent