Sentry

"A Sentry SDK for Java, Android and other JVM languages."

Sentry performs software error monitoring and performance monitoring to help developers diagnose, fix, and optimize the performance of their code. Sentry supports more than 30 coding languages, and integrates to tools like GitHub, Slack, and Jira.

In Sentry:

Get and record the following details from Sentry UI: they will be required later in this procedure.

1. auth-token :

   • Login to your Sentry account (if your organization has an special account for third-party integrations you should use that account to create the auth-token).
   • After login, go to https://sentry.io/settings/account/api/auth-tokens/

   

   • Click Create New Token.

   • Under the Create New Token section select the following scopes:

     • project:read
     • team:read
     • org:read
     • member:read
     • project:releases
     • event:read

     

   • Click Create Token.

   • Click the copy icon beside the Client Secret field; temporarily save the secret token value for later use in the Relyance AI configuration steps.

   • Click Save.

2. product: Tenant-specific product name that you want to associate with in the integration analysis.

In Relyance AI:

1. Login to your Relyance AI account.
2. Navigate to the Settings (bottom-left corner).
3. Select Integrations.
4. Search and locate the Sentry 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, seeIntegration Features.
8. In the Connection section, provide the appropriate values and click on Continue,
   • Connection Name: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by Discovery Source across the Inventory, Visual Maps, Assets, and Data Flow Analysis pages.
   • Rescan Frequency: This property allows you to configure how often Relyance executes scans against this Vendor connection.
   • Business Atlas Associations (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the Select Associations dropdown — the wizard will not advance past this step without one. For more details, see Business Atlas.
9. In the Authentication section, provide the details captured from the Sentry application and click on Authenticate.
   • Product
   • OAuth
10. 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.
11. Review the configuration summary from the Completion section and click on Finish.
12. Confirm the integration Status reflects Connected.

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.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. 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.

resource "relyance_integration_connection" "sentry" {
  vendor = "sentry"
  name   = "<your connection name>"

  auth = {
    method = "account-credentials"
    # NOTE: accounts carries credentials (token) but is not flagged
    # secret, so it goes in params and IS written to Terraform state in
    # cleartext. Keep state in an encrypted remote backend with restricted
    # access, and rotate the credential if state was ever committed.
    params = {
      accounts = jsonencode([
        {
          auth-token = ""
          product = ""
        }
      ])
      data_storage_location = "us"
    }
  }

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