Sentry supports data forwarding to Segment, Amazon SQS, and Splunk, but has no native connector to data warehouses such as Snowflake or BigQuery. Enterprise customers with internal data lakes want to join Sentry error data with proprietary event streams (e.g., gameplay telemetry) without paying for duplicate storage.
- Existing forwarders: Segment, Amazon SQS, Splunk (error events only; no spans/logs)
- No first-class Snowflake, BigQuery, or generic data lake export
- SQS is the closest DIY path but requires significant customer-side infrastructure
Add first-class data warehouse export connectors (Snowflake and/or BigQuery as initial targets) with full event type coverage including errors, spans, and logs.
Reported by a gaming console customer (Triiodide Technologies).
Action taken on behalf of Richard Propst.
Sentry supports data forwarding to Segment, Amazon SQS, and Splunk, but has no native connector to data warehouses such as Snowflake or BigQuery. Enterprise customers with internal data lakes want to join Sentry error data with proprietary event streams (e.g., gameplay telemetry) without paying for duplicate storage.
Add first-class data warehouse export connectors (Snowflake and/or BigQuery as initial targets) with full event type coverage including errors, spans, and logs.
Reported by a gaming console customer (Triiodide Technologies).
Action taken on behalf of Richard Propst.