Skip to content

Improvements for auto memory dump collection #4013

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

Open
bruno-garcia opened this issue Feb 28, 2025 · 1 comment
Open

Improvements for auto memory dump collection #4013

bruno-garcia opened this issue Feb 28, 2025 · 1 comment

Comments

@bruno-garcia
Copy link
Member

we need to say what the threshold was. Was it X% etc?

Image

Image

Not sure the stack trace helps here. Might be because of AttachStacktrace

Image

https://github.com/getsentry/symbol-collector/blob/6a67b120c928b1fea79ecf8c6365d3a3fa862eeb/src/SymbolCollector.Server/appsettings.json#L24

In that case nothing for us to do here. But it'll group everything based on the stack trace.
So we could at least set a Fingerprint, and group by "new ["MemoryDumpDetection", trigger.ToString()]`. So that we have different groups depending on what the trigger is. So if we change the trigger, we get a new issue.
And the trigger could be on the title/message too so it's easier to tell them apart.

@bruno-garcia
Copy link
Member Author

Relates to:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants