Data Forwarding

Sentry provides the ability to forward processed error events to certain third-party providers, namely Segment, Amazon SQS, and Splunk.

This is often useful when you may want to analyze exceptions more deeply, or empower other teams, such as a Business Intelligence function.

Only error events will be forwarded. Forwarding of transaction events is not supported.

Configure Data Forwarding for your organization by navigating to Settings » Data Forwarding, then providing the required information for the given integration. Note that only one org-level forwarder can be created for each integration. However, configs can be overridden with project overrides.

Amazon SQS

Integration with Amazon SQS makes it quick and easy to pipe exceptions back into your own systems.

The payload for Amazon is identical to our standard API event payload, and will evolve over time. For more details on the format of this data, see our API documentation.

Segment

The Segment integration will generate Error Captured events within your data pipeline. These events will only be captured for error events, and only when an ID is present the user context. The general shape of the event will look roughly similar to:

{
  "userId": "1",
  "event": "Error Captured",
  "properties": {
    "environment": "production",
    "eventId": "002c8bbde8324dae9f12a0b96f5b1e51",
    "exceptionType": "ValueError",
    "release": "a2def1",
    "transaction": "/api/0/users/{user}/",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0",
    "page": {
      "url": "https://sentry.io/api/0/users/{user}/",
      "method": "GET",
      "search": "",
      "referer": "https://sentry.io/"
    }
  },
  "timestamp": "2017-05-20T15:29:06Z"
}

Splunk

For details on the Splunk integration, visit the dedicated Splunk integration documentation.