getsentry / getsentry/sentry-dotnet
Improvements for auto memory dump collection
- Dominant language
- C#
- Stars
- 770
- Forks
- 248
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 49
Description
> we need to say what the threshold was. Was it X% etc?
> Not sure the stack trace helps here. Might be because of `AttachStacktrace`
[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.
Contributor guide
Assessment
This issue has not been assessed yet.