Data Forwarding

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

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

Configure Data Forwarding by navigating to your [Project] » Settings » Data Forwarding, then providing the required information for the given integration.

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

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.

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": "{user}/",
      "method": "GET",
      "search": "",
      "referer": ""
  "timestamp": "2017-05-20T15:29:06Z"

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

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").