Sentry Integration

Connect Sentry to Scoutflo to bring application errors, performance issues, and events

Once configured, Scoutflo can:

• Correlate Sentry issues with Kubernetes events, deployments, and infra changes

• Surface Sentry errors directly inside investigation timelines

• Use Sentry as a signal source for alerting and post‑incident analysis

---

✅ Prerequisites

Before setting up the Sentry integration, ensure you have:

• A Sentry account (cloud‑hosted or self‑hosted) with administrative access to create API tokens / internal integrations

• Access to Scoutflo’s Integrations tab in the platform UI

• For self‑hosted Sentry:

  • The hostname of your Sentry server (for example, https://sentry.yourdomain.com)

• Basic familiarity with Sentry’s organization and project structure:

  • Which org / projects map to the services you want Scoutflo to analyze

If you don’t have these, coordinate with your SRE / Platform / Security team before proceeding.

---

🧩 Setup Guide

To connect Sentry to Scoutflo, you’ll:

1. Create an Internal Integration in Sentry

2. Configure the required scopes

3. Copy and paste the API token into Scoutflo

4. (Optional) Configure self‑hosted Sentry

This enables Scoutflo’s AI engine to access Sentry data for debugging and monitoring.

---

Step 1: Create an Internal Integration in Sentry

1. Log in to your Sentry account (cloud or self‑hosted).

2. In the left sidebar, go to Settings → Developer Settings.

3. Click Create New Integration.

4. Select Internal Integration.

5. Provide a descriptive name, for example:

   • Scoutflo Integration

   • Scoutflo AI SRE

6. Confirm creation.

Sentry will now show a configuration page for this internal integration.

---

Step 2: Configure required scopes

Assign the following read‑only permissions so Scoutflo can fetch the data it needs:

• Project: Read

  • Allows Scoutflo to list and retrieve project details

  • Used for operations like sentry-list-projects

• Issue & Event: Read

  • Enables access to issues and events metadata

  • Used for operations like sentry-get-issue-details, sentry-search-events

• Organization: Read

  • Permits retrieval of organization‑wide data (teams, alert rules, etc.)

  • Used for operations like sentry-list-organizations, sentry-list-alert-rules

Make sure all three scopes are selected. Save the integration configuration when done.

💡Tip: Keep the integration scope as narrow as possible while still including all of the above read permissions.

---

Step 3: Copy and paste the API token into Scoutflo

After you configure scopes, Sentry will generate an API token for this internal integration.

1. On the Sentry integration page, locate the token (often highlighted or shown in red).

2. Copy the token carefully and store it temporarily in a secure place.

3. In a new tab, open the Scoutflo platform UI.

4. Navigate to Integrations → Observability → Sentry.

5. Paste the API token into the Sentry API Token field.

6. Provide any additional required fields, for example:

   • Organization slug

   • Default project (optional, depending on your setup)

7. Click Save or Connect to apply the configuration.

Once saved, Scoutflo will attempt to validate the token and reach Sentry’s APIs.

Treat this token like any other secret. Do not commit it to Git, store it in plain text, or share it in chat without redaction.

---

Step 4: Configure self‑hosted Sentry (optional)

If you are using self‑hosted Sentry instead of sentry.io:

1. In Scoutflo’s Integrations → Sentry panel, locate the Sentry Host / Base URL field.

2. Enter the hostname of your Sentry server, for example:

   • https://sentry.yourdomain.com

3. Ensure that this hostname is:

   • Reachable from Scoutflo (or the Scoutflo Satellite, if used)

   • Using a valid TLS certificate (for HTTPS)

4. Click Test connection (if available) or Save to apply the settings.

5. If the test fails, verify DNS, TLS, and firewall / network policies.

---

✅ Post‑setup validation

After configuring Sentry, do these quick checks:

1. Test the connection in Scoutflo

   • In Integrations → Sentry, use the Test connection or Validate action.

   • Confirm the status shows the integration as Connected.

2. Verify projects and issues

   • From Scoutflo, list Sentry projects and make sure the ones you expect are visible.

   • Open one project and confirm that recent issues can be fetched.

3. Verify alerts and incident flow

   • Trigger a test alert in Sentry.

   • Check that it appears in Scoutflo’s alerts / incidents view and in any connected channels (for example, Slack), if you’ve enabled those.

---

Troubleshooting Common Issues

• Invalid API token: Double‑check that the token is copied exactly (no extra spaces or missing characters). If problems continue, revoke the old token in Sentry and generate a new one.

• Insufficient scopes: Make sure the integration in Sentry has all required scopes enabled: Project: Read, Issue & Event: Read, and Organization: Read. Save the changes and retry the connection.

• Self‑hosted connectivity: Verify that the Sentry URL (including https://) is correct and reachable from your environment. Review firewall rules, proxies, or network policies if the connection still fails.

• No alerts received: Check that Sentry alert rules are correctly configured and active (for example, by listing or reviewing alert rules and sending a test alert). Confirm that the Sentry integration in Scoutflo is marked as connected and monitoring the expected projects/environments.

---