feat(gsAdmin): add customer abuse stats section#110292
Draft
priscilawebdev wants to merge 22 commits intomasterfrom
Draft
feat(gsAdmin): add customer abuse stats section#110292priscilawebdev wants to merge 22 commits intomasterfrom
priscilawebdev wants to merge 22 commits intomasterfrom
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.