Skip to content

feat(gsAdmin): add customer abuse stats section#110292

Draft
priscilawebdev wants to merge 22 commits intomasterfrom
priscila/feat/customer-abuse-stats
Draft

feat(gsAdmin): add customer abuse stats section#110292
priscilawebdev wants to merge 22 commits intomasterfrom
priscila/feat/customer-abuse-stats

Conversation

@priscilawebdev
Copy link
Member

@priscilawebdev priscilawebdev commented Mar 10, 2026

Adds abuse period visualization to the existing customer stats chart in admin views.

Instead of a separate chart, abuse periods are shown as red mark area overlays on the existing stats chart, making it easy to correlate abuse with other metrics regardless of data type (errors, transactions, spans, etc.). Abuse data is fetched separately since abuse outcomes only exist under the error category.

  • Highlights abuse periods as red mark areas on the chart
  • Shows abuse value on hover via a custom tooltip
  • Works across all data type tabs, not just errors
  • Handles missing/empty abuse reasons

@linear-code
Copy link

linear-code bot commented Mar 10, 2026

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 10, 2026
@priscilawebdev priscilawebdev changed the title feat(gsAdmin): add customer abuse stats tab feat(gsAdmin): add customer abuse stats section Mar 10, 2026
priscilawebdev and others added 3 commits March 10, 2026 12:37
Move abuse region visualization from a separate tab into the main
customer stats chart as a mark area overlay with an interactive
tooltip. Remove the standalone customerAbuseStats component and
its tab from customer/project details views.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add non-null assertions for array access and cast mark area series
to SeriesItem to satisfy BarChartSeries type constraint.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant