Skip to main content
There’s no such thing as a stupid question. On this page, you’ll find the answers to the ones we’re asked most frequently. If you need further support, please check out our support page

​
Contents

​
Getting Started

​
I Need Help Getting Started. Where Do I Begin?

If you’re new to AppSignal or want to know more about configuring AppSignal features, please read our guides

​
AppSignal Libraries

​
What Programming Languages Does AppSignal Support?

AppSignal supports the Node.js, Ruby and Elixir programming languages. We also have JavaScript packages for catching client-side errors in supported browsers.

​
Filtering Data

​
How Do I Ignore Actions in My Application?

You can Ignore Actions to stop recording data for specific actions, requests, background jobs, etc.

​
How Do I Ignore Errors in My Application?

You can Ignore Errors (based on their name) to prevent AppSignal from reporting and alerting you to them.

​
How do I Filter Data That’s Sent to AppSignal?

To learn how to filter the data that is sent to AppSignal, read one of the following guides:

​
How do I Add Additional Instrumentation to My Application?

Additional instrumentation can be added to your application to give you more insights into how your application is performing by measuring the duration of separate events. Lean how in the documentation for our Ruby Gem and Elixir Package.

​
What Is the Difference Between setRootName and setName?

setName and setRootName both rename spans, but at different levels. setName sets the name of an individual span as it appears in the performance sample timeline, while setRootName sets the name of the root transaction — what you see in the performance overview and transaction list. A good pattern is to call setRootName once on your outermost handler (for example, `${request.method} ${pattern}` to produce a title like GET /users/:id), and use setName together with setCategory on inner spans such as middleware, loaders, and actions, so they appear as clearly labeled events in the timeline breakdown. For more on naming and adding spans, see the Node.js instrumentation guide.

​
How Do I Run Multiple Applications on One Host?

By default AppSignal is configured to assume one application runs on one host. If you run more than one application on a host, some unexpected behavior may occur, such as data being reported for a different application. To configure AppSignal for multiple applications on one host the AppSignal Working Directory needs to be configured. Read more about how to configure the working directory in our Guide to Running Multiple Application on One Host

​
What Operating Systems Does AppSignal Support?

Please read our Operating Systems page for the full list of supported Operating Systems and any required packages.

​
How Do I Debug an Issue with the AppSignal Integration?

Please read our Debugging Guide for a complete guide to AppSignal Integration debugging issues. You can also check our Known Issues page for issues that may be present in your version of the AppSignal Integration.

​
User Account

​
How Do I Enable Two-Factor Authentication (2FA) For the AppSignal App?

Please refer to our Two-Factor Authentication page for more information on enabling 2FA.

​
Why Aren’t My Two-Factor Authentication (2FA) Codes Working?

If your authenticator app’s codes are rejected when you log in, the most common cause is clock drift on the device generating them. Two-factor authentication codes are time-based (TOTP), so that device’s clock must be accurate — this often breaks after changing time zones. Enable automatic (network) date and time on the device, then try the newly generated code. If you still can’t log in, use one of the five recovery codes you saved when you enabled 2FA to bypass two-factor authentication. See Two-Factor Authentication for more on recovery codes.

​
What IP Addresses does AppSignal Use?

Currently the AppSignal Push API uses the following IP addresses: 
185.191.3.93
185.191.3.94
185.191.3.125
185.191.3.126
Currently the AppSignal webhooks orginate from the following IP addresses: 
185.191.3.107
185.191.3.72
185.191.3.116
185.191.3.84
We don’t recommend allowlisting specific IP addresses. They might change, and more may be added in the future, for instance, when we need to cycle our load balancers or quickly add servers. If you decide to allowlist our IP addresses, please send our support team an email, we’ll do our best to notify you if there are upcoming changes.

​
Errors & Performance

​
Why Is My Performance Issue Always Marked as Closed?

An issue’s Open or Closed status is determined by its notification settings, not by whether the underlying problem is still happening. AppSignal marks an issue as Open when it sends a notification for it. Performance issues use the “Never Notify” setting by default, so no notification is sent — which is why they stay Closed. To have a performance issue open on new occurrences, change its notification setting, either per issue or by updating your organization-level default. See Notification settings for how to configure this.

​
How Do I See Error Counts Per Namespace?

To see error counts per namespace, create a Number chart that uses the transaction_exception_count metric (AppSignal’s count of errors recorded in an application), filtered by the namespace tag:
  1. Open the application you want to measure, go to Dashboards, and add a new chart.
  2. Select the Number tab.
  3. Set the metric to transaction_exception_count.
  4. Add the namespace tag and enter the namespace name (for example, web or background).
  5. Set the aggregation type to Total value.
  6. Create the chart.
The chart shows the total error count for that namespace over the time frame you select when viewing it. AppSignal stores error data separately per application, so there is no single total across all applications — create one chart per namespace per application, and add the counts together yourself if you need an overall figure.