Skip to main content
The following list includes all configuration options with the name of the environment variable and the name of the key in the configuration file. For more information on how to configure the Standalone AppSignal Agent with a configuration file or using environment variables, see our configuration section.

​
Available options

​
app_name

​
Description

Name of your application as it should be displayed on AppSignal.com.
Note: Changing the name or environment of an existing app will create a new app on AppSignal.com.

​
environment

​
Description

The environment of the app to be reported to AppSignal.
Note: Changing the name or environment of an existing app will create a new app on AppSignal.com.

​
push_api_key

​
Description

The organization-level authentication key to authenticate with our Push API. Read more about the AppSignal Push API key.

​
bind_address

​
Description

A valid IPv4 address the AppSignal agent uses as a binding for its TCP and UDP servers. Use a specific address if you only want the agent to listen to requests made to that address. Set this option to 0.0.0.0 to allow to receive requests from hosts using any IP address. By default it only listens to requests made on the same host. This option is applied to all the agent servers (StatsD, OpenTelemetry and NGINX).

​
ca_file_path

​
Description

  • Configure the path of the SSL certificate file.
Use this option to point to another certificate file if there’s a problem connecting to our API.
Note: The specified path cannot contain Operating Specific file system abstractions, such as the homedir symbol ~ for *NIX systems. This will be seen as a malformed path.

​
cpu_count

​
Description

The available CPU capacity of the host, in number of CPUs. This is used to calculate the CPU usage percentage in the host metrics. If not set, the agent will attempt to automatically detect this from cgroups. The number of CPUs can be a fraction, e.g. 0.5.

​
dns_servers

​
Description

Configure DNS servers for the AppSignal agent to use.
YAML
If you’re affected by our DNS timeouts, try setting a DNS server manually using this option that doesn’t use more than 4 dots in the server name.
  • Acceptable values: 8.8.8.8, my.custom.local.server.
  • Not acceptable values: foo, my.awesome.custom.local.dns.server.
If the DNS server cannot be reached the agent will fall back on the host’s DNS configuration and output a message in the appsignal.log file: A problem occurred while setting DNS servers.

​
enable_host_metrics

​
Description

Set this option to false to disable host metrics collection. On Heroku and Dokku host metrics are disabled by default. This is done because these systems will report inaccurate metrics from within the containers. Host metrics collection on these systems cannot be enabled. For Heroku, use the Heroku log drain instead.

​
enable_http

​
Description

Set this option to true to enable the OpenTelemetry HTTP server. When enabled, the AppSignal agent will listen to a localhost-bound server on port 8099. If you’re running several AppSignal-instrumented applications in the same server, this configuration option can only be enabled in one of them. This is required for apps using the OpenTelemetry HTTP exporter to report data to AppSignal.

​
enable_nginx_metrics

​
Description

Set to true to enable the NGINX metrics server. See the NGINX metrics documentation for details. When enabled, the AppSignal agent will listen to a localhost-bound server on port 27649. If you’re running several AppSignal-instrumented applications in the same server, this configuration option can only be enabled in one of them.

​
enable_opentelemetry_http

​
Description

Set this option to true to enable the OpenTelemetry HTTP server. When enabled, the AppSignal agent will listen to a localhost-bound server on port 8099. If you’re running several AppSignal-instrumented applications in the same server, this configuration option can only be enabled in one of them. This is required for apps using the OpenTelemetry HTTP exporter to report data to AppSignal.

​
enable_statsd

​
Description

Enables the StatsD server in the AppSignal agent. When enabled, the AppSignal agent will listen to a localhost-bound server on port 8125. If you’re running several AppSignal-instrumented applications in the same server, this configuration option can only be enabled in one of them.

​
filter_parameters

​
Description

List of parameter keys that should be ignored using AppSignal filtering. Their values will be replaced with [FILTERED] when transmitted to AppSignal.
TOML
Read more about parameter filtering.

​
filter_session_data

​
Description

List of session data keys that should be ignored using AppSignal filtering. Their values will be replaced with [FILTERED] when transmitted to AppSignal.
TOML
Read more about session data filtering.

​
host_role

​
Description

Group hosts by role and generate metrics based on this role. One such metric is the reporting_hosts counter metric. A good role indicates what the main role of the server is, like “webserver”, “processor”, “api”, “database”, “loadbalancer”, etc.

​
hostname

​
Description

This overrides the server’s hostname. Useful for when you’re unable to set a custom hostname or when a nondescript id is generated for you on hosting services.

​
http_proxy

​
Description

If you require the agent to connect to the Internet via a proxy set the complete proxy URL in this configuration key.

​
ignore_actions

​
Description

With this config option you can specify a list of actions that will be ignored by AppSignal. Everything that happens including exceptions will not be transmitted to AppSignal. This can be useful to ignore health check endpoints or other actions that you don’t want to monitor. Read more about ignoring actions.

​
ignore_errors

​
Description

List of error classes that will be ignored. Any exception raised with this error class will not be transmitted to AppSignal. Read more about ignoring errors.

​
ignore_namespaces

​
Description

List of namespaces that will be ignored. Any error raised or slow request that occurs in this namespace will not be send to AppSignal. Read more about namespaces.

​
log_level

​
Description

This option sets the severity level of AppSignal’s internal logger and does not affect the logging feature.
Set the severity level of AppSignal’s internal logger. If it is configured to “info” it will log all error, warning and info messages, but not log the debug messages. Setting it to the levels “debug” or “trace” is usually only needed on request from support. Setting the level to “debug”/“trace” could have a slight impact on the disk usage and IO, especially on high-traffic sites. CPU overhead is minimal with the debug option enabled. Accepted values:
  • error
  • warning
  • info
  • debug
  • trace

​
nginx_port

​
Description

Configure the port on which the NGINX metrics server is exposed. When AppSignal receives NGINX metrics, it listens on a localhost-bound server, by default on port 27649. If you’re running several AppSignal-instrumented applications in the same server with NGINX metrics enabled, use this option to configure each application to listen on a different port.

​
opentelemetry_port

​
Description

Set this option to configure the OpenTelemetry HTTP server port of the AppSignal agent process. Configure this port if another process is already running on the machine that is also using this port to avoid conflicts.

​
push_api_endpoint

​
Description

Configure the endpoint to send data to AppSignal. This setting will not have to be changed.

​
running_in_container

​
Description

AppSignal expects to be running on the same machine between different deploys. Set this key to true if the application is running in a container, such as with Docker. Newer versions of the AppSignal integration automatically detect its container environment, so no manual configuration is necessary. If you’re having trouble with the automatic detection, please contact support. This option is set to true automatically on Heroku.

​
send_environment_metadata

​
Description

Send environment metadata about the app. For more information please read about environment metadata.

​
send_params

​
Description

Whether to skip sending request parameters to AppSignal. For more information please read about send_params in filtering request parameters.

​
send_session_data

​
Description

Set this option to false to not send any session data with exception traces and performance issue samples. For more information please read about request session data filtering.

​
statsd_port

​
Description

Set this option to configure the StatsD HTTP server port of the AppSignal agent process. Configure this port if another process is already running on the machine that is also using this port to avoid conflicts.

​
working_dir_path

​
Description

Override the location where the Standalone AppSignal Agent can store temporary files. Use this option if the default location is not suitable. See our how AppSignal operates page for more information about the purpose of this working directory.
Note: The specified path cannot contain Operating Specific file system abstractions, such as the homedir symbol ~ for *NIX systems. This will be seen as a malformed path.