You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: