On this page we list some frequently asked questions, if you need further support please check out our support section.
- Getting started
- AppSignal libraries
- What programming languages does AppSignal support?
- Filtering data
- How to add additional instrumentation to my app?
- How to run multiple applications on one host?
- What Operating Systems does AppSignal support?
- How to debug an issue with the AppSignal integration?
- User account
If you're new to AppSignal or want to know more about to configure AppSignal features, please read our guides to get set up.
By ignoring actions it's possible to not record any data for the configured actions, requests, background jobs, etc.
By ignoring errors AppSignal will ignore errors matching the exact name of an error.
- Filter request parameters and background job arguments.
- Filter session data for HTTP requests.
- Filter HTTP request headers.
Add additional instrumentation to your app to gain more insights in how your application is performing by measuring the duration of separate events. Read how in the documentation for our Ruby gem and Elixir package.
By default AppSignal is configured to assume one application runs on one host. If you run more than one application on a host, some odd behavior may occur, such as data being reported for a different app.
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.
Please see our Operating Systems page for the full list of support Operating Systems and what packages it requires.
Please see our debugging guide for a complete guide to debug issues with the AppSignal integration.
Also check our known issues page for issues that may be present in your version of the AppSignal integration.
Please see our two-factor authentication page for more information.
At the time of writing, the AppSignal push API uses one of the following IP addresses:
1 2 3 4 5 6 188.8.131.52 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124 126.96.36.199
We don't recommend whitelisting specific IP addresses. They might change and/or more might be added in the future, for instance when we need to quickly add servers or cycle our loadbalancers. If you do decide to whitelist these IP addresses, please send our support team an email, and we'll do our best to notify you if there are upcoming changes.