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

Evaluate effectiveness of current frontend debugging tools and determine next steps #3650

Open
3 tasks
doug-s-nava opened this issue Jan 27, 2025 · 0 comments
Open
3 tasks

Comments

@doug-s-nava
Copy link
Collaborator

Summary

When discussing frontend logging, it became clear that we are unsure where the holes are in our current ability to debug important production issues related to the frontend or from frontend error reports.

The idea is that we will perform a simulation of a production issue in DEV, and a group of engineers will attempt to solve the issue, in the process identifying what tools are available for diagnosing the issue, and where deficiencies are. After performing the test we'll create new tickets for follow up work to make our debugging abilities more robust.

Acceptance criteria

  • a plan is created for the error simulation
  • error simulation is performed
  • new tickets are created for all next steps to improve instrumentation / logging / tooling
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant