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.

Sign up for GitHub

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

Jump to bottom

Find best way for contract between sentry & relay to communicate "too large" outcome reasoning #87168

Closed
matejminar opened this issue Mar 17, 2025 · 2 comments
Closed

Find best way for contract between sentry & relay to communicate "too large" outcome reasoning #87168

matejminar opened this issue Mar 17, 2025 · 2 comments
Assignees
@priscilawebdev

Comments

@matejminar
Copy link
Member

  • Ingest are currently working on disambiguating the "too large" discard reason, adding which part of the discarded payload was too large. They asked for help in figuring out what to do with this reason and how not to break outcomes for our user-facing & admin stats.

  • See feat(outcomes): add item type to invalid outcome relay#4558 for the relay draft PR
@tobias-wilfert
Copy link
Member

For context we already have: #87078

@priscilawebdev
Copy link
Member

closing this as it was already done by @tobias-wilfert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@priscilawebdev priscilawebdev

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@matejminar @priscilawebdev @tobias-wilfert