[SERVER-64880] Clarify all DSI error logging Created: 24/Mar/22 Updated: 29/Mar/22 Resolved: 28/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mridul Augustine (Inactive) | Assignee: | Mridul Augustine (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | dp-qp-stakeholder-request-2022-01 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.3, v5.2, v5.0, v4.4, v4.2, v4.0
|
||||||||
| Sprint: | TIPS 2022-04-04 | ||||||||
| Participants: | |||||||||
| Story Points: | 0 | ||||||||
| Description |
|
From stakeholder spreadsheet, requested by Samy: Debugging while creating a new workload is difficult. It's hard to tell if the issue is related to the code for a new workload, a bug in DSI, or a bug in the server. For example, sometimes it's unclear why a perf workload failed and requires searching through all the logs carefully to find the issue. There are a lot of red herrings, so maybe one possible idea is to create a debugging guide. Proposed solution: Make sure error logs explicitly mention where the error comes from, e.g., infrastructure versus user workload. Update docs if necessary to clarify any errors. Timebox this investigation to 2 days. |
| Comments |
| Comment by Mridul Augustine (Inactive) [ 28/Mar/22 ] |
|
No server side change required |