Description:
To assist future debugging and better operational capacity, it would be ideal to be able to easily find the relevant logging for a given parsing session for a file upload.
Acceptance Criteria:
[ ] Proposed and actionable plan for implementation without significant infrastructure lift (ideally, backend-only or with lightweight microservice)
[ ] System admin should intuitively be able to find the parser output for a given datafile (stt/qtr/section)
[ ] Testing Checklist has been run and all tests pass
[ ] README is updated, if necessary
Tasks:Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
[ ] Spike
[ ] Run Testing Checklist and confirm all tests pass
Notes:
Utilize duplicate django logging, store file via s3? Alternatively, lightweight microservice like logstash or sentry per comment below in open questions.
Supporting Documentation:
Open Questions:
Do we need 831 or can we MVP this via only backend?
3122 Review: How do we want a log file to look and be useful both for per-field validation but also at a callstack level showing positively each step taken?
andrew-jameson
commented
2 months ago
Description: To assist future debugging and better operational capacity, it would be ideal to be able to easily find the relevant logging for a given parsing session for a file upload.
Acceptance Criteria:
Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
Notes: Utilize duplicate django logging, store file via s3? Alternatively, lightweight microservice like logstash or sentry per comment below in open questions.
Supporting Documentation:
Open Questions: