---
title: Sentry
description: See Sentry exceptions in your Datadog event stream.
breadcrumbs: Docs > Integrations > Sentry
---

# Sentry
Integration version2.0.0
## Overview{% #overview %}

Sentry has deprecated legacy webhook integrations and now recommends using **Sentry Internal Integrations** with webhooks to forward events to external systems.

To forward events to Datadog, you must configure a webhook integration directly in Sentry. This setup allows Sentry to send events to a public endpoint of your choice supported by your organization.

More information and setup instructions are available in [Sentry's official documentation](https://docs.sentry.io/organization/integrations/integration-platform/webhooks/).

You can find the Datadog intake URL (for logs or events) in the [Datadog API documentation](https://docs.datadoghq.com/api/latest/logs.md#send-logs) or Datadog account settings.

## Legacy Webhooks{% #legacy-webhooks %}

If you previously configured Sentry's legacy webhook integration, it may continue to function for now. However, **all new webhook setups must use Sentry's Internal Integrations** going forward.

## Setup{% #setup %}

### Configuration{% #configuration %}

## Step 1: Deploy the Webhook Forwarder{% #step-1-deploy-the-webhook-forwarder %}

Sentry webhooks cannot include custom headers. You must deploy a small service on your infrastructure that:

- Accepts incoming webhook POSTs from Sentry
- Adds required authentication headers
- Forwards the payload to your destination

For more information, see the official [Sentry documentation](https://docs.sentry.io/organization/integrations/integration-platform/webhooks/).

## Step 2: Create an Internal Integration in Sentry{% #step-2-create-an-internal-integration-in-sentry %}

1. Navigate to **Settings > Developer Settings > Internal Integrations**.

1. Click **Create New Internal Integration**.

1. Fill in:

   - **Name**: Alert Forwarder
   - **Webhook URL**: The public URL of your deployed service
   - Enable **Alert Rule Action**

1. Set Permissions:

   - **Issue & Event**: Read
   - **Alerts**: Read

1. Enable Webhook Triggers:

   - `issue`
   - `error`

1. Click **Save**.

1. Optionally generate a token if your proxy supports token-based authentication.

## Step 3: Create an Alert Rule{% #step-3-create-an-alert-rule %}

1. Navigate to **Project Settings > Alerts > Issue Alerts**.

1. Create a new alert rule:

   - **WHEN**: A new issue is created
   - (Optional) Add filters
   - **THEN**: Send a notification using your internal integration
   - Set frequency and notification interval as needed

1. Use the **Send Test Notification** option to verify the setup.

## Step 4: Confirm Receipt{% #step-4-confirm-receipt %}

Once configured:

- Monitor your destination system for forwarded alerts.
- Confirm the payload structure and content match expectations.
- Use logs from your proxy to debug delivery issues.

If alerts are not appearing:

- Ensure your proxy is reachable from the public internet.
- Validate that authentication headers are being correctly added.
- Review Sentry's webhook logs under **Developer Settings > Internal Integrations > Your Integration > Logs**.

## Support{% #support %}

If you have questions or run into issues configuring Sentry's webhook integration, please reach out directly to Sentry Support:[https://support.sentry.io](https://support.sentry.io)

## Further Reading{% #further-reading %}

- [Collaborative Bug Fixing with Datadog's Sentry Integration](https://www.datadoghq.com/blog/datadog-sentry-integration-collaborative-bug-fixing/)