getsentry / getsentry/sentry

Enhanced Aggregates Capabilities in Sentry Logs

Open
#104,093 7 comments 1 reaction 0 assignees View on GitHub
Feature Product Area: Performance
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

We’ve been reviewing Sentry’s capabilities and identified several limitations that make it difficult to perform product-level analysis, even though the underlying data exists. While Sentry is excellent for error tracking and performance monitoring, the following features would significantly improve its utility for product analytics:
- Support for calculating percentages of users who go from A → B vs A → X, based on existing navigation and interaction logs.
- Average Time per Page. Ability to compute time differences between navigation spans to measure time-on-page.
- Ability to identify the first navigation span in each trace for better understanding of user entry points.

### Solution Brainstorm

_No response_

### Product Area

Dashboards

Contributor guide

Open the contributing guide

Research direction

Start by reviewing Sentry's dashboard aggregation capabilities and the existing navigation and interaction logs described in the issue. Done would mean defining and implementing support for user-path percentages, time per page, and first-navigation-span analysis.

Written by the indexing model from the issue text.

Assessment

Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.