Sentry

Sentry integration enables Scoutflo to access error tracking and monitoring data, including projects, issues, events, releases, and alert rules, to enhance AI-driven debugging workflows. By connecting Sentry to Scoutflo, the AI Engine fetches detailed error data, correlate it with Kubernetes or CI/CD events (e.g., via ArgoCD or Prometheus), and provide precise root cause analysis and remediation suggestions. This integration is critical for diagnosing application-level issues, such as unhandled exceptions or performance bottlenecks, in Kubernetes-based environments.

Key Features

  • Error Analysis: Retrieve stack traces, error messages, and event details to pinpoint issues like null pointer exceptions or API failures.

  • Release Correlation: Link errors to specific releases or commits (via sentry-list-releases, sentry-get-release-details) for deployment-related debugging.

  • Alert Management: Monitor and manage Sentry alert rules (via sentry-list-alert-rules, sentry-create-alert-rule) to ensure timely notifications and rapid response.

  • Automated Fixes: Initiate AI-driven fixes for simple issues using sentry-begin-autofix, reducing manual intervention.

Prerequisites

Before setting up the Sentry integration, ensure the following:

  • A Sentry account (cloud-hosted or self-hosted) with administrative access to create API tokens.

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

  • For self-hosted Sentry instances, the hostname of your Sentry server.

  • Familiarity with Sentry’s organization and project structure to select the appropriate scopes.

Setup Guide

To connect Sentry to Scoutflo, follow these steps to generate and configure an API token with the required permissions. This enables Scoutflo’s AI Engine to access Sentry data for debugging and monitoring.

Step 1: Create an Internal Integration

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

  2. Navigate to Settings > Developer Settings in the Sentry dashboard.

  3. Click Create New Integration and select Internal Integration.

  4. Provide a name for the integration (e.g., “Scoutflo Integration”) and confirm creation.

Step 2: Configure Required Scopes

Assign the following permissions to ensure Scoutflo can access necessary data:

  • Project: Read – Allows Scoutflo to list and retrieve project details (e.g., via sentry-list-projects).

  • Issue & Event: Read – Enables access to issues, events, and their details (e.g., via sentry-get-issue-details, sentry-search-events).

  • Organization: Read – Permits retrieval of organization-wide data, such as teams and alert rules (e.g., via sentry-list-organizations, sentry-list-alert-rules).

Step 3: Copy and Paste the API Token

  1. After configuring scopes, Sentry will generate an API token (displayed in red).

  2. Copy the token securely.

  3. In Scoutflo’s platform UI, navigate to the Integrations tab.

  4. Select Sentry and paste the token into the provided field.

  5. Save the configuration to activate the integration.

Step 4: Configure Self-Hosted Sentry (If Applicable)

For self-hosted Sentry instances:

  1. In Scoutflo’s Integrations tab, locate the Sentry configuration panel.

  2. Enter the hostname of your self-hosted Sentry server (e.g., https://sentry.yourdomain.com).

  3. Verify connectivity by testing the integration in Scoutflo’s UI.

  4. Save the configuration to complete setup.

Post-Setup Validation

After configuring the integration:

  • Use Scoutflo’s UI to test the connection, ensuring the AI Engine can query Sentry data (e.g., via sentry-validate).

  • Confirm that projects and issues are accessible by running a test query, such as listing projects with sentry-list-projects.

  • Check that alerts are being received in Scoutflo (or via Slack, if integrated) to verify notification flow.

Troubleshooting Common Issues

  • Invalid API Token: Ensure the token is copied correctly without extra spaces. Regenerate the token in Sentry if issues persist.

  • Insufficient Scopes: Verify that all required scopes (Project: Read, Issue & Event: Read, Organization: Read) are enabled. Update the integration in Sentry if needed.

  • Self-Hosted Connectivity: Confirm the hostname is correct and accessible from Scoutflo’s network. Check firewall rules or network policies if the connection fails.

  • No Alerts Received: Use sentry-list-alert-rules to verify alert rule configurations and ensure they are firing as expected.

PreviousMonitoringNextAlerting

Last updated