Skip to content
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

Relay doesn't add outcomes/meta info if attachment is too large #4534

Open
bruno-garcia opened this issue Feb 27, 2025 · 0 comments
Open

Relay doesn't add outcomes/meta info if attachment is too large #4534

bruno-garcia opened this issue Feb 27, 2025 · 0 comments
Assignees

Comments

@bruno-garcia
Copy link
Member

bruno-garcia commented Feb 27, 2025

When an envelope with an event + attachment is sent, but the attachment is dropped due to being too large.
How about we annotate the event ("had an attachment of N MB (if we know the size, I believe we cut the stream so..) but got dropped)

Relates to:

This is a new feature of the .NET SDK, to get a heap dump (counts of allocated objects per type). I'm hoping to add this to the preview button so you can check the dump in Sentry: https://github.com/getsentry/dotnet-heapview
But the dump was too large and got dropped.

The SDK logs go to GCP (Symbol Collector) and I got:

2: 161153506
@l: "Warning"
@mt: "{0}: Attachment '{1}' dropped because it's too large ({2} bytes)."

but if it wasn't for me logging the Sentry SDK on a logging tool, I would have no idea what's going on

Replaces (private):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants