Open dachakra opened 11 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-settings-integrations for triage ⏲️
@dachakra Sessions is a different dataset and has much larger volumes than error events. I'll track this in the backlog but I doubt we'll be getting to this in the next few quarters
@dachakra is the customer using sessions for mobile projects mainly? How would they like to use this sessions data?
The use case is native applications (C/C++) Their goal is to use the session data in conjunction with error data to provide KPIs around their applications. Although we provide aggregated metrics such as crash-free rates, they would like to conduct a more in-depth analysis.
Another use case would be to tie session data to other analytics data points that are available outside of Sentry.
Given the concern of session data volume, a suggestion would be to enforce a volume limit for the data forwarded.
Problem Statement
As an analytics team, we need to analyze project session data in correlation with error data and utilize data points from other data analytics tools alongside Sentry. This will enable us to provide meaningful Key Performance Indicators (KPIs) and metrics for our leadership teams.
Solution Brainstorm
"We should enhance the data forwarding process to SQS by allowing not just error events but also session events to be forwarded. This would be an optimal solution. Or provide a webhook to allow data forwarding.
Product Area
Settings - Integrations