Ignore empty environment variables for config options

Added

• Add the appsignal.config.otp_app resource attribute config option. When set for Elixir applications, we will use the OTP app name to detect which stacktrace lines originate from the app, and which lines are from dependencies.

Changed

• Consider empty environment variables as unset. From now on, an environment variable that's set to an empty string is considered unset when reading the collector configuration from system environment variables.

  In the example below, the environment variable will be considered unset. It will not fail on parsing an empty string as a number and set the default HTTP port instead.

  Shell

  APPSIGNAL_HTTP_PORT=""
  

  This behavior is changed for the following config options:

  • APPSIGNAL_CPU_COUNT
  • APPSIGNAL_ENABLE_HOST_METRICS
  • APPSIGNAL_FILES_WORLD_ACCESSIBLE
  • APPSIGNAL_HOSTNAME
  • APPSIGNAL_HTTP_PORT
  • APPSIGNAL_LOG_LEVEL
  • APPSIGNAL_PUSH_API_ENDPOINT
  • APPSIGNAL_PUSH_API_KEY
  • APPSIGNAL_RUNNING_IN_CONTAINER

• In the appsignal/collector Docker image we will now listen to the PORT environment variable if it's set, and use it to configure the HTTP server's port.

  If the APPSIGNAL_HTTP_PORT environment variable is also set in addition to the PORT environment variable, it will read from the APPSIGNAL_HTTP_PORT environment variable.

This release can be installed through our collector packages and Docker image.