AppSignal Standalone agent configuration
Configuring the AppSignal standalone agent is important because, without it, the standalone agent won't know which application it is reporting data for.
In this documentation we'll explain how and what can be configured in the standalone agent and how the configuration is loaded.
Minimal configuration
With a minimal configuration AppSignal will receive enough information to report the data collected by the agent from one of your apps.
A minimal configuration requires the following configuraiton options to be set:
Configuration methods
Configuration file
The AppSignal standalone agent can be configured with a configuration file. This method is required for the Linux package installation method.
You need to find, or create, the configuration file at /etc/appsignal-agent.conf. Once you've found or created a configuration file can then configure the agent with the config options listed on the options page.
Example configuration file
Below is an example of an appsignal-agent.conf configuration file.
For the full list of options, please see the configuration options page.
# /etc/appsignal-agent.conf push_api_key = "0000-0000-0000-000" app_name = "My app name" environment = "production" hostname = "hostname"
System environment variable
Another way of configuring AppSignal is by using system environment variables on the host the application AppSignal is monitoring is running on.
This configuration method is used by the standalone agent Docker image. It can also be used for the Linux package in combination with the configuration file.
Make sure these environment variables are configured in the way that's compatible with your Operating System and that the configuration get loaded before the standalone agent is started.
The configuration options page lists each config option's equivalent system environment variable. You can use these variables to configure the standalone agent, for example when configuring your app name:
# Common Linux Bash example export APPSIGNAL_APP_NAME="My app"