> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Honeybadger

> Error tracking — users & access

<Tabs>
  <Tab title="Overview">
    Connect Honeybadger with a personal auth token to sync account users, projects, and faults, and run access reviews. Read-only.

    <Info>
      **Read-only access.** DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
    </Info>

    <Note>
      DSALTA collects this integration's data when you connect it — you can refresh it at any time with **Sync from integrations** on the **Integrations** page. The compliance checks below re-run once a day at 02:00 America/New\_York.
    </Note>

    ## What DSALTA reads

    DSALTA reads the Honeybadger user roster — names, emails and roles, which appears on your **Access** page; and your Honeybadger resources, which appear on your **Inventory** page; and incidents, which appear on your **Incidents** page. Every Honeybadger member is listed as Active. DSALTA syncs the **first** account the token can see (the first result from `/accounts/`), and that account's users, projects and faults are what the access checks run against — so create the token in the account you want monitored.

    It calls these Honeybadger endpoints:

    * `/accounts/`
    * `/accounts/{accountId}/users`
    * `/projects`
    * `/projects/{projectId}/faults`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Honeybadger environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection fails to validate">
        Invalid token.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        Open **Integrations** in the DSALTA sidebar, stay on the **Connected** tab, and click **Manage** on the integration's card. Open the **Status** tab: it shows either **Connected and working properly** or **Connection issues detected**.

        Use the **Status** tab, not **Overview** — Overview always reports **Connected** regardless of the real state.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        On an integration-powered check, **Failed** normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to **Source Data**, and read the result code: **403** is a missing permission, **428** is a setting DSALTA still needs, **500** is a failure on DSALTA's side.

        A real compliance gap shows **207** and leaves the test looking **Completed**. See [Understanding Test Results](/guides/data-library/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        Compliance checks re-run once a day at 02:00 America/New\_York. To refresh sooner, open **Integrations → Connected** and click **Sync from integrations** at the top right — it refreshes every connected integration at once.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **Disconnecting is destructive and cannot be undone.** DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see [Integration errors](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        That is expected. **Configure scope** is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    A Honeybadger personal authentication token (HTTP Basic auth, blank password). Read-only.

    **Before you begin**

    * A Honeybadger account (free plan works)

    You will need:

    | Field                   | Where to find it                              | Example                           |
    | ----------------------- | --------------------------------------------- | --------------------------------- |
    | **Personal Auth Token** | [Open](https://app.honeybadger.io/users/edit) | `Honeybadger personal auth token` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Honeybadger**, and click **Connect** to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
      </Step>

      <Step title="Open your Honeybadger profile">
        Go to app.honeybadger.io/users/edit — this opens **User settings**.
      </Step>

      <Step title="Copy your personal auth token">
        In **User settings**, click **API Access** in the left sidebar, then copy the value under **Personal API Key**. Honeybadger labels it "Personal API Key"; that is the personal auth token DSALTA needs.

        <Tip>Honeybadger's Data API allows **360 requests per hour** per token and returns HTTP 403 once you exceed it. DSALTA pages through every project's faults on each sync, so if you share this token with other tooling a sync can be rejected — give DSALTA its own personal API key rather than reusing one.</Tip>

        <Tip>Do not click **Reset personal API key** on that screen after connecting — it issues a new key and invalidates the one DSALTA holds. There is no Reconnect button in DSALTA, so recovering means Disconnect and connect again, which permanently deletes the data and tests already collected from Honeybadger.</Tip>

        <img src="https://mintcdn.com/dsalta/4UzgskHSsjeDN5e5/images/integrations/honeybadger/01-honeybadger-personal-api-key.png?fit=max&auto=format&n=4UzgskHSsjeDN5e5&q=85&s=01ae77f4721a0e272440743c06d61293" alt="Honeybadger User settings with API Access selected, showing the Personal API Key and a Reset personal API key button" style={{maxWidth:"720px",width:"100%",borderRadius:"8px"}} width="2916" height="1264" data-path="images/integrations/honeybadger/01-honeybadger-personal-api-key.png" />
      </Step>

      <Step title="Connect Honeybadger">
        Paste your personal auth token, then click Connect.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential when you click **Connect**. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** Invalid token.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance.

    | Check                                                                                                                      | Severity | What it verifies                                                                       |
    | -------------------------------------------------------------------------------------------------------------------------- | -------- | -------------------------------------------------------------------------------------- |
    | [User access to Critical System should be valid](/integrations/honeybadger/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Honeybadger access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/honeybadger/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Honeybadger access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                                       |
    | ------- | ------------------------------------------------------------------------------------------ |
    | Setup   | [Find your Honeybadger personal auth token](https://app.honeybadger.io/users/edit)         |
    | Setup   | [Honeybadger Data API — getting started](https://docs.honeybadger.io/api/getting-started/) |
    | General | [Honeybadger website](https://honeybadger.io)                                              |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)                    |
  </Tab>
</Tabs>