> ## Documentation Index > Fetch the complete documentation index at: https://docs.appsignal.com/llms.txt > Use this file to discover all available pages before exploring further. # Node.js package configuration options 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 AppSignal with a configuration file or system environment variables, see our [Configuration](/nodejs/3.x/configuration) topic. ## Available options * Required options * [`active`](#option-active) * [`environment`](#option-environment) * [`name`](#option-name) * [`pushApiKey`](#option-pushapikey) * Options * [`additionalInstrumentations`](#option-additionalinstrumentations) * [`bindAddress`](#option-bindaddress) * [`caFilePath`](#option-cafilepath) * [`cpuCount`](#option-cpucount) * [`debug`](#option-debug) * [`disableDefaultInstrumentations`](#option-disabledefaultinstrumentations) * [`dnsServers`](#option-dnsservers) * [`enableHostMetrics`](#option-enablehostmetrics) * [`enableMinutelyProbes`](#option-enableminutelyprobes) * [`enableNginxMetrics`](#option-enablenginxmetrics) * [`enableOpentelemetryHttp`](#option-enableopentelemetryhttp) * [`enableStatsd`](#option-enablestatsd) * [`filesWorldAccessible`](#option-filesworldaccessible) * [`filterParameters`](#option-filterparameters) * [`filterSessionData`](#option-filtersessiondata) * [`hostname`](#option-hostname) * [`hostRole`](#option-hostrole) * [`httpProxy`](#option-httpproxy) * [`ignoreActions`](#option-ignoreactions) * [`ignoreErrors`](#option-ignoreerrors) * [`ignoreLogs`](#option-ignorelogs) * [`ignoreNamespaces`](#option-ignorenamespaces) * [`log`](#option-log) * [`logLevel`](#option-loglevel) * [`logPath`](#option-logpath) * [`nginxPort`](#option-nginxport) * [`opentelemetry_port`](#option-opentelemetry_port) * [`requestHeaders`](#option-requestheaders) * [`revision`](#option-revision) * [`runningInContainer`](#option-runningincontainer) * [`sendEnvironmentMetadata`](#option-sendenvironmentmetadata) * [`sendParams`](#option-sendparams) * [`sendSessionData`](#option-sendsessiondata) * [`statsdPort`](#option-statsdport) * [`workingDirectoryPath`](#option-workingdirectorypath) ## active | Field | Value | | ---------------------- | -------------------------- | | Config file key | `active` | | System environment key | `APPSIGNAL_ACTIVE` | | Required | yes | | Type | Boolean (`true` / `false`) | | Default value | `false` | ### Description Configure AppSignal to be active or not for a given environment. Most commonly used in the [file configuration](/nodejs/3.x/configuration) per environment. ## environment | Field | Value | | ---------------------- | ------------------------------------------------------------------------ | | Config file key | `environment` | | System environment key | `APPSIGNAL_APP_ENV` | | Required | yes | | Type | `String` | | Default value | `Read from environment variable `NODE\_ENV`, defaults to "development".` | ### Description The environment of the app to be reported to AppSignal. **Note**: Changing the [name](#option-name) or environment of an existing app will create a new app on AppSignal.com. ## name | Field | Value | | ---------------------- | -------------------- | | Config file key | `name` | | System environment key | `APPSIGNAL_APP_NAME` | | Required | yes | | Type | `String` | | Default value | `nil` | ### Description Name of your application as it should be displayed on AppSignal.com. **Note**: Changing the name or [environment](#option-env) of an existing app will create a new app on AppSignal.com. ## pushApiKey | Field | Value | | ----------------------- | -------------------------------------------------------------------------------- | | Config file key | `pushApiKey` | | System environment key | `APPSIGNAL_PUSH_API_KEY` | | Required | yes | | Type | `String` | | Default value | `null` (unset by default) | | Available since version | `2.2.5` | | | | ### Description The organization-level authentication key to authenticate with our Push API. Read more about the [AppSignal Push API key](/appsignal/terminology#push-api-key). ## additionalInstrumentations | Field | Value | | ----------------------- | ---------------------------- | | Config file key | `additionalInstrumentations` | | Required | no | | Type | `list(String)` | | Default value | `[]` | | Available since version | `3.0.0` | ### Description List of additional OpenTelemetry instrumentations to use with AppSignal, via third-party libraries or your own integrations. ## bindAddress | Field | Value | | ----------------------- | ------------------------ | | Config file key | `bindAddress` | | System environment key | `APPSIGNAL_BIND_ADDRESS` | | Required | no | | Type | `String` | | Default value | `127.0.0.1` | | Available since version | `3.0.15` | ### 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](#option-enable_statsd), [OpenTelemetry](#option-enable_opentelemetry_http) and [NGINX](#option-enable_nginx_metrics)). ## caFilePath | Field | Value | | ---------------------- | -------------------------------- | | Config file key | `caFilePath` | | System environment key | `APPSIGNAL_CA_FILE_PATH` | | Required | no | | Type | `String` | | Default value | Packaged `cacert.pem` file path. | ### Description 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. ## cpuCount | Field | Value | | ----------------------- | --------------------- | | Config file key | `cpuCount` | | System environment key | `APPSIGNAL_CPU_COUNT` | | Required | no | | Type | `Float` | | Default value | `undefined` | | Available since version | `3.3.2` | ### 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`. ## debug | Field | Value | | ----------------------- | --------------------------------------------------------------------------------------------------------------- | | Config file key | `debug` | | System environment key | `APPSIGNAL_DEBUG` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `false` | | Available since version | `1.0.0` | | | | ### Description **Warning**: This config option is deprecated in Node.js package 2.2.6. Please use the [`logLevel`](#option-loglevel) option instead for Node.js package 2.2.6 and newer. Enable debug logging, this is usually only needed on request from support. With this option enabled AppSignal will log a lot more information about decisions that are made during metrics collection and when data is sent to AppSignal.com servers. Enabling debug logging 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. This option sets the severity level of AppSignal's internal logger. This configuration option does not affect the [logging feature](/logging). ## disableDefaultInstrumentations | Field | Value | | ----------------------- | -------------------------------------------- | | Config file key | `disableDefaultInstrumentations` | | System environment key | `APPSIGNAL_DISABLE_DEFAULT_INSTRUMENTATIONS` | | Required | no | | Type | `list(String)` or Boolean (`true` / `false`) | | Default value | `false` | | Available since version | `3.0.0` | ### Description Allows you to disable the automatic instrumentation of default integrations: * @appsignal/opentelemetry-instrumentation-bullmq * @opentelemetry/instrumentation-amqplib * @opentelemetry/instrumentation-express * @opentelemetry/instrumentation-fastify * @opentelemetry/instrumentation-graphql * @opentelemetry/instrumentation-http * @opentelemetry/instrumentation-ioredis * @opentelemetry/instrumentation-knex * @opentelemetry/instrumentation-koa * @opentelemetry/instrumentation-mongodb * @opentelemetry/instrumentation-mongoose * @opentelemetry/instrumentation-mysql2 * @opentelemetry/instrumentation-mysql * @opentelemetry/instrumentation-nestjs-core * @opentelemetry/instrumentation-pg * @opentelemetry/instrumentation-redis * @opentelemetry/instrumentation-redis-4 * @opentelemetry/instrumentation-restify * @opentelemetry/instrumentation-undici * @prisma/instrumentation To disable all instrumentations, set the value to `true`. ## dnsServers | Field | Value | | ---------------------- | ----------------------- | | Config file key | `dnsServers` | | System environment key | `APPSIGNAL_DNS_SERVERS` | | Required | no | | Type | `list(String)` | | Default value | `[]` | ### Description Configure DNS servers for the AppSignal agent to use. ```sh Shell theme={null} # In the host environment export APPSIGNAL_DNS_SERVERS="8.8.8.8,8.8.4.4" ``` If you're affected by our [DNS timeouts](/support/known-issues#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`. ## enableHostMetrics | Field | Value | | ---------------------- | ------------------------------- | | Config file key | `enableHostMetrics` | | System environment key | `APPSIGNAL_ENABLE_HOST_METRICS` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | \`\`true` / detected by system` | ### Description Set this option to `false` to disable [host metrics](/metrics/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](/heroku/host-metrics) instead. ## enableMinutelyProbes | Field | Value | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Config file key | `enableMinutelyProbes` | | System environment key | `APPSIGNAL_ENABLE_MINUTELY_PROBES` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `true` | | Available since version | `0.4.0` | | | | ### Description Enables the [minutely probes](/nodejs/3.x/instrumentation/minutely-probes) system. ## enableNginxMetrics | Field | Value | | ----------------------- | -------------------------------- | | Config file key | `enableNginxMetrics` | | System environment key | `APPSIGNAL_ENABLE_NGINX_METRICS` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `false` | | Available since version | `3.0.8` | ### Description Set to `true` to enable the NGINX metrics server. [See the NGINX metrics documentation for details.](/metrics/nginx) 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. ## enableOpentelemetryHttp | Field | Value | | ----------------------- | ------------------------------------- | | Config file key | `enableOpentelemetryHttp` | | System environment key | `APPSIGNAL_ENABLE_OPENTELEMETRY_HTTP` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `true` | | Available since version | `3.1.0` | ### Description Set this option to `true` to enable the [OpenTelemetry HTTP server](/standalone-agent/installation). 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. ## enableStatsd | Field | Value | | ----------------------- | -------------------------- | | Config file key | `enableStatsd` | | System environment key | `APPSIGNAL_ENABLE_STATSD` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `false` | | Available since version | `2.2.2` | ### Description Enables the [StatsD server](/standalone-agent/statsd) 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. ## filesWorldAccessible | Field | Value | | ----------------------- | ---------------------------------- | | Config file key | `filesWorldAccessible` | | System environment key | `APPSIGNAL_FILES_WORLD_ACCESSIBLE` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `true` | | Available since version | `2.2.4` | ### Description If this is set to `true` the [AppSignal working directory](/appsignal/how-appsignal-operates#working-directory) that is created is accessible for all users (Unix permissions `0666`). This is often necessary because processes for the same app run under a different user. Set to `false` to disable this behaviour (Unix permissions `0644`). ## filterParameters | Field | Value | | ----------------------- | ----------------------------- | | Config file key | `filterParameters` | | System environment key | `APPSIGNAL_FILTER_PARAMETERS` | | Required | no | | Type | `list(String)` | | Default value | `[]` | | Available since version | `2.2.5` | ### Description List of parameter keys that should be ignored using AppSignal filtering. Their values will be replaced with `[FILTERED]` when transmitted to AppSignal. Read more about [parameter filtering](/application/parameter-filtering). ## filterSessionData | Field | Value | | ----------------------- | ------------------------------- | | Config file key | `filterSessionData` | | System environment key | `APPSIGNAL_FILTER_SESSION_DATA` | | Required | no | | Type | `list(String)` | | Default value | `[]` | | Available since version | `2.2.5` | ### Description List of session data keys that should be ignored using AppSignal filtering. Their values will be replaced with `[FILTERED]` when transmitted to AppSignal. Read more about [session data filtering](/application/session-data-filtering). ## hostname | Field | Value | | ---------------------- | -------------------- | | Config file key | `hostname` | | System environment key | `APPSIGNAL_HOSTNAME` | | Required | no | | Type | `String` | | Default value | detected from system | ### 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. ## hostRole | Field | Value | | ----------------------- | ------------------------- | | Config file key | `hostRole` | | System environment key | `APPSIGNAL_HOST_ROLE` | | Required | no | | Type | `String` | | Default value | `null` (unset by default) | | Available since version | `3.0.19` | ### 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. ## httpProxy | Field | Value | | ---------------------- | ------------------------- | | Config file key | `httpProxy` | | System environment key | `APPSIGNAL_HTTP_PROXY` | | Required | no | | Type | `String` | | Default value | `null` (unset by default) | ### Description If you require the agent to connect to the Internet via a proxy set the complete proxy URL in this configuration key. ## ignoreActions | Field | Value | | ---------------------- | -------------------------- | | Config file key | `ignoreActions` | | System environment key | `APPSIGNAL_IGNORE_ACTIONS` | | Required | no | | Type | `list(String)` | | Default value | `[]` | ### 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](/guides/filter-data/ignore-actions). ## ignoreErrors | Field | Value | | ---------------------- | ------------------------- | | Config file key | `ignoreErrors` | | System environment key | `APPSIGNAL_IGNORE_ERRORS` | | Required | no | | Type | `list(String)` | | Default value | `[]` | ### 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](/guides/filter-data/ignore-errors). ## ignoreLogs | Field | Value | | ----------------------- | ----------------------- | | Config file key | `ignoreLogs` | | System environment key | `APPSIGNAL_IGNORE_LOGS` | | Required | no | | Type | `list(String)` | | Default value | `[]` | | Available since version | `3.4.0` | ### Description List of log messages that will be ignored. Any log message containing any of the elements of the list will not be transmitted to AppSignal. A small subset of regex syntax is supported, read more about it in our [Ignore Logs](/guides/filter-data/ignore-logs) guide. ## ignoreNamespaces | Field | Value | | ---------------------- | ----------------------------- | | Config file key | `ignoreNamespaces` | | System environment key | `APPSIGNAL_IGNORE_NAMESPACES` | | Required | no | | Type | `list(String)` | | Default value | `[]` | ### 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](/application/namespaces). ## log | Field | Value | | ---------------------- | --------------- | | Config file key | `log` | | System environment key | `APPSIGNAL_LOG` | | Required | no | | Type | `String` | | Default value | `file` | ### Description This option configures what logger that AppSignal's internal logging functionality will use and does not affect the [logging feature](/logging). **Note**: The [AppSignal agent](/appsignal/how-appsignal-operates), which is used by the integration, will always write to the "appsignal.log" file. Select which logger the AppSignal integration will use. Accepted values are `file` and `stdout`. See also the `log_path` configuration. * `file` (default) * Write all AppSignal logs to the file system. * `stdout` (default on [Heroku](https://heroku.com)) * Print AppSignal logs in the parent process' STDOUT instead of to a file. Useful with hosting solutions such as container systems and Heroku. ## logLevel | Field | Value | | ----------------------- | --------------------- | | Config file key | `logLevel` | | System environment key | `APPSIGNAL_LOG_LEVEL` | | Required | no | | Type | `String` | | Default value | `info` | | Available since version | `2.2.6` | ### Description This option sets the severity level of AppSignal's internal logger and does not affect the [logging feature](/logging). 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 ## logPath | Field | Value | | ---------------------- | -------------------- | | Config file key | `logPath` | | System environment key | `APPSIGNAL_LOG_PATH` | | Required | no | | Type | `String` | | Default value | `/tmp` | ### Description This option configures the location of AppSignal's internal logging file and does not affect the [logging feature](/logging).
**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. Override the location of the path (directory) where the `appsignal.log` file can be written to. ## nginxPort | Field | Value | | ----------------------- | ---------------------- | | Config file key | `nginxPort` | | System environment key | `APPSIGNAL_NGINX_PORT` | | Required | no | | Type | `Integer` | | Default value | `27649` | | Available since version | `3.6.7` | ### 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 | Field | Value | | ----------------------- | ------------------------------ | | Config file key | `opentelemetry_port` | | System environment key | `APPSIGNAL_OPENTELEMETRY_PORT` | | Required | no | | Type | `String` | | Default value | `8099` | | Available since version | `3.1.0` | ### 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. ## requestHeaders | Field | Value | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | Config file key | `requestHeaders` | | System environment key | `APPSIGNAL_REQUEST_HEADERS` | | Required | no | | Type | `list(String)` | | Default value | `["accept", "accept-charset", "accept-encoding", "accept-language", "cache-control", "connection", "content-length", "range"]` | | Available since version | `2.2.5` | ### Description The `requestHeaders` config option contains a list of HTTP request headers which are read and stored by the AppSignal Node.js package. This `requestHeaders` config option is an *allowlist*, which means that it will only take headers as specified by this config option. If this config option is unset it will use the AppSignal default. Following list is the AppSignal package default. ```javascript Node.js theme={null} client = Appsignal.new( // ...Other config opts requestHeaders: [ "accept", "accept-charset", "accept-encoding", "accept-language", "cache-control", "connection", "content-length", "range" ] ) ``` To configure AppSignal to not store any HTTP request headers on AppSignal transactions, configure the option with an empty list. ```javascript Node.js theme={null} client = Appsignal.new( // ...Other config opts requestHeaders: [] ) ``` ## revision | Field | Value | | ----------------------- | ----------------------------------------------------------------------------------------------------------------- | | Config file key | `revision` | | System environment key | `APP_REVISION` | | Required | no | | Type | `String` | | Default value | `null` (unset by default) | | Available since version | `1.0.0` | | | | ### Description Set the app revision to report the currently running version of your app. AppSignal will create a deploy marker when this value changes, and tag all incoming data with the current revision. When your application is deployed using Kamal, or when it is deployed to Render, or when it is deployed to Heroku and the [Heroku Labs: Dyno Metadata](https://devcenter.heroku.com/articles/dyno-metadata) feature is enabled, the AppSignal integration will automatically detect the Git commit of the current deployment and use it as the revision. You can overwrite the automatically detected revisions in Heroku, Render or Kamal by manually setting the `revision` config option to a custom value. Read more about deploy markers in the [deploy markers topic](/application/markers/deploy-markers). ## runningInContainer | Field | Value | | ---------------------- | -------------------------------- | | Config file key | `runningInContainer` | | System environment key | `APPSIGNAL_RUNNING_IN_CONTAINER` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | detected by agent | ### 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](mailto:support@appsignal.com). This option is set to `true` automatically on [Heroku](http://heroku.com/). ## sendEnvironmentMetadata | Field | Value | | ----------------------- | ------------------------------------- | | Config file key | `sendEnvironmentMetadata` | | System environment key | `APPSIGNAL_SEND_ENVIRONMENT_METADATA` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `true` | | Available since version | `2.2.6` | ### Description Send environment metadata about the app. For more information please read about [environment metadata](/application/environment-metadata). ## sendParams | Field | Value | | ----------------------- | -------------------------- | | Config file key | `sendParams` | | System environment key | `APPSIGNAL_SEND_PARAMS` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `true` | | Available since version | `2.2.8` | ### Description Whether to skip sending request parameters to AppSignal. For more information please read about [send\_params](/application/parameter-filtering) in filtering request parameters. ## sendSessionData | Field | Value | | ----------------------- | ----------------------------- | | Config file key | `sendSessionData` | | System environment key | `APPSIGNAL_SEND_SESSION_DATA` | | Required | no | | Type | Boolean (`true` / `false`) | | Default value | `true` | | Available since version | `2.2.9` | ### 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](/application/session-data-filtering). ## statsdPort | Field | Value | | ----------------------- | ----------------------- | | Config file key | `statsdPort` | | System environment key | `APPSIGNAL_STATSD_PORT` | | Required | no | | Type | `Integer` | | Default value | `8125` | | Available since version | `3.0.16` | ### 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. ## workingDirectoryPath | Field | Value | | ----------------------- | ---------------------------------- | | Config file key | `workingDirectoryPath` | | System environment key | `APPSIGNAL_WORKING_DIRECTORY_PATH` | | Required | no | | Type | `String` | | Default value | detected by agent | | Available since version | `1.0.0` | ### Description Override the location where AppSignal for Node.js can store temporary files. Use this option if the default location is not suitable. See our [how AppSignal operates](/appsignal/how-appsignal-operates) page for more information about the purpose of this working directory. If you are running multiple applications using AppSignal on the same server, use this configuration option to select different working directories for every AppSignal instance, otherwise the two instances could conflict with one another. For more information on this scenario see our [running multiple applications on one host](/guides/application/multiple-applications-on-one-host) documentation. ```javascript Node.js theme={null} // Example: appsignal.js const { Appsignal } = require("@appsignal/nodejs"); const appsignal = new Appsignal({ // Other config workingDirectoryPath: "/tmp/project_1" }); ``` **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.