-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attach stack trace to events from HTTPClient
integration so they are not merged (fingerprinted) into a single issue
#8353
Comments
Thanks for writing in! This is a very valid point. We'll try to fix this. |
Hi @lforst any update on this? |
@harry-gocity nope you would see it in this issue! |
Hi @lforst just wondering if you could give any estimates as to if/when this would hit roadmap for a Sentry release. We currently have 8.4k events all grouped in Sentry under the same I'm currently upgrading us from |
@harry-gocity There are no real changes besides the renaming of it. We are currently not working on this issue and likely won't do so for the coming month. I cannot give a timeline. We do not have any specific recommendations for grouping. Adding custom grouping in beforeSend seems fine to me. |
Is there any solution for this or an eta for a fix? |
@bryanjtc No, this feature just needs some love. It's not really a bug, but the created errors need proper stacktraces and grouping. |
Do you have an example for a better grouping strategy using beforeSend? |
@bryanjtc I guess you could look at the sentry-javascript/packages/browser/src/integrations/httpclient.ts Lines 360 to 384 in 08a3b7c
|
HTTPClient
integration incorrectly merged into single issueHTTPClient
integration so they are not merged (fingerprinted) into a single issue
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
7.53.1
Framework Version
React 17.0.2, Next.js 12.1.6
Link to Sentry event
https://go-city.sentry.io/issues/4231630878/?project=4503958434480128
SDK Setup
Steps to Reproduce
We added the HTTP Client Integration to our Sentry setup:
After this, we started to see events being tracked in Sentry for 500, 502 and 504 status codes in responses from our site.
Expected Result
We would be able to triage requests to different URLS separately. Sentry would group
HTTPClient
-captured events as separate issues. We thought that would happen by default using the request url and response status code.Actual Result
All the events are grouped under the same Sentry issue, regardless of the error code or request URL.
For the issue linked above:
Under the 'all events' tab there several different issues all being grouped together (URLs cropped intentionally):
AFAIK we have not accidentally merged any issues manually.
The text was updated successfully, but these errors were encountered: