# AppSignal

![Image 1 of 1](https://assets.relyanceuat.xyz/images/docs/34756175642253/34756175619853.png)
AppSignal is a real-time APM provider for Ruby, Rails, Node.js, and Elixir & Phoenix. It provides insights into errors and performance issues, plus host monitoring and an easy-to-use custom metrics platform.

In order to integrate AppSignal with Relyance AI you will need the **App** **ID** and Personal API **Token.** You will also need to provide a **Product** name that your would associate with the integration analysis.

#### In AppSignal:

1. Login to your AppSignal account.
2. Click on the Application you wish monitor with Relyance and go to the dashboard.
3. Copy the **App ID** from your web-browsers URL. It is found between 'sites/' and '/dashboard'. e.g.: https://appsignal.com/boutique/sites/ **93457f4b83abcdefhij00000** /dashboard
4. Click on the user profile menu in the top right-hand corner and select **Account settings**.
5. In the Account **Personal** settings scroll to the bottom and find the **API** section.
6. Copy your personal API **Token**.

![AppSignal-3.png](https://assets.relyanceuat.xyz/images/docs/34756175642253/34756175624461.png)

![AppSignal-4.png](https://assets.relyanceuat.xyz/images/docs/34756175642253/34756155195533.png)

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **AppSignal** integration card and click on it.
5. Click on the **Add Connection** button on the top right
6. Provide a meaningful name for the integration and click on the **Add** button
7. In the **Overview** section, select the integration features you wish to enable for the integration, review the **Scope and Permission**, and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/) In the **Connection** section, provide the appropriate values and click on **Continue**, [](/docs/other-settings/business-atlas-overview/)

![Screenshot 2025-11-06 115816.png](https://assets.relyanceuat.xyz/images/docs/34756175642253/40915649522701.png)

![Screenshot 2025-11-06 115919.png](https://assets.relyanceuat.xyz/images/docs/34756175642253/40915649523981.png)

8. This step applies only if the **Data Inspection** check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., unlikely) offer more coverage but may produce false positives, while higher sensitivity (e.g., very likely) provides greater accuracy but less coverage.
9. In the Authentication section, edit the JSON by adding **App ID**, **Token**, and **Product** name into the JSON in the respective quotes in the form.
10. Review the configuration summary from the Completion section and click on Finish.  Confirm the integration Status reflects Connected

![Screenshot](https://assets.relyanceuat.xyz/images/docs/34756175642253/41104991155469.png)

![Screenshot 2025-11-06 120015.png](https://assets.relyanceuat.xyz/images/docs/34756175642253/40915609648525.png)

![Screenshot 2025-11-06 120114.png](https://assets.relyanceuat.xyz/images/docs/34756175642253/40915649525133.png)

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **A credential rotated at the vendor is not picked up here.** **Personal Token** is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.
2. **One entry can be empty while the others work.** **Account Details** is a list, and each entry is authorised independently, so a missing grant on one account or subscription empties just that entry -- silently.

<!-- failure-modes:end -->

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Custom** | `Personal Token` (secret), `Account Details` | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "appsignal" {
  vendor = "appsignal"
  name   = "<your connection name>"

  auth = {
    method = "access-token"
    params = {
      accounts = jsonencode([
        {
          api-key = ""
          app-id = ""
          product = ""
        }
      ])
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      personal_token = var.appsignal_personal_token
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->