Sentry

Crawler

Overview

Connect Sentry to Datadog to:

• See exceptions in the stream, in real time
• Search for exceptions in your graphs
• Discuss exceptions with your team

Setup

Installation

Setting up Sentry integration:

1. Log into Sentry
2. Navigate to a Project
3. Navigate to Project’s Settings Page
4. On the left side, click Legacy Integrations
5. Scroll down to the Webhooks integration, click the slider toggle to enable it, and then click Configure Plugin
6. Under Callback URLs’, enter https://app.datadoghq.com/intake/webhook/sentry?api_key=<YOUR_DATADOG_API_KEY>
7. Click Save changes

By default, Sentry pings the Webhook with event data every time there is a new exception (as opposed to a new instance of an already-logged exception). If you want different (or additional) triggers, you can configure them in the Alerts section of your project settings.

Adding a host name to Sentry errors (Optional)

Occasionally, the server name which Sentry reports may not match the host name recognized by Datadog. To overcome this, set a custom value for the server_name tag which is attached to each event.

To use a different host name while preserving Sentry’s default server_name value, you can alternatively set a hostname tag on your events. See the dedicated Sentry Tagging Event documentation to learn how to do this for your language.

Troubleshooting

Why aren’t my Sentry errors showing up in Datadog?

Your Sentry Webhook probably isn’t triggering. This could be caused by:

• Alerts are only sent when a rule is triggered:
  For example, if the rule condition is when “an event is first seen”, an alert will not be dispatched until a new issue is created. (Depending on how many unique issues your project is receiving, this can take some time.)

• The notification integration is disabled:
  Ensure that the notification integration is enabled under the rule actions, either as the specific service, or covered under “all enabled services”.