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

Report failing network requests for hard-to-repro flows #6781

Closed
gomesalexandre opened this issue Apr 30, 2024 · 0 comments · Fixed by #6782
Closed

Report failing network requests for hard-to-repro flows #6781

gomesalexandre opened this issue Apr 30, 2024 · 0 comments · Fixed by #6782

Comments

@gomesalexandre
Copy link
Contributor

gomesalexandre commented Apr 30, 2024

Overview

We currently have many tickets opened for hard to repro flows.

Example include:
#6775
#6766
#6684 (comment)
#6763
#6762

All were raised over the last few days and were unable to be repro'd.

Instead of guesstimating here, trying to repro and failing to, either because that was a transient issue with nodes or upstream service (e.g Li.Fi), or a very specific payload that was sent as a result of a race condition or very specific conditions, we should have observability in the failed network requests to help engineering with debugging and monkey patching/reproduction in an effort to solve those issues.

References and additional details

Acceptance Criteria

  • Failed network requests are reported using sentry or similar

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

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

Successfully merging a pull request may close this issue.

1 participant