feat: add support for multiple issue types with n+1 performance issues #23
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.
Extend the error generator to support multiple Sentry issue types beyond errors. This adds an issue type selector with Error and Performance options (user feedback and dead clicks shown as coming soon).
The Performance issue type generates N+1 API call detection by making parallel GET requests to a target endpoint and sending the transaction envelope directly to Sentry's API. This allows testing performance issue detection in any Sentry project via DSN.
Changes:
The N+1 detection follows Sentry's requirements: minimum 10 parallel GET requests with
http.clientspans within aui.actiontransaction.